archive/rsnext
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
rsnext/test/turbopack-tests-manifest.json

15483 lines
1.1 MiB
JSON
Raw Normal View History

Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
{
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/font/src/google/find-font-files-in-css.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"findFontFilesInCss should find all font files and preload requested subsets",
"findFontFilesInCss should not return duplicate font files when several variants use the same font file"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/font/src/google/get-font-axes.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
"getFontAxes errors Invalid axes value",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"getFontAxes errors Invalid value in axes array",
"getFontAxes errors Setting axes on font without definable axes"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/font/src/google/loader.test.ts": {
"passed": [
"next/font/google loader URL from options Albert_Sans",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/font/google loader URL from options Ballet",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"next/font/google loader URL from options Fraunces",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/font/google loader URL from options Inter",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"next/font/google loader URL from options Molle",
"next/font/google loader URL from options Nabla",
"next/font/google loader URL from options Oooh_Baby",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/font/google loader URL from options Poppins",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"next/font/google loader URL from options Roboto",
"next/font/google loader URL from options Roboto Mono",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/font/google loader URL from options Roboto_Flex",
"next/font/google loader URL from options Source_Sans_3"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/font/src/google/sort-fonts-variant-values.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"sortFontsVariantValues should correctly compare and return result for comma-separated values",
"sortFontsVariantValues should correctly compare and return result for plain integer values",
"sortFontsVariantValues should sort an array of plain integer values correctly",
"sortFontsVariantValues should sort an array of values with comma-separated values correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/font/src/google/validate-google-font-function-call.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"validateFontFunctionCall errors Invalid display value",
"validateFontFunctionCall errors Invalid subset in call",
"validateFontFunctionCall errors Missing function name",
"validateFontFunctionCall errors Missing subsets in config and call",
"validateFontFunctionCall errors Missing weight for non variable font",
"validateFontFunctionCall errors Setting axes on non variable font",
"validateFontFunctionCall errors Unknown font",
"validateFontFunctionCall errors Unknown style",
"validateFontFunctionCall errors Unknown weight",
"validateFontFunctionCall errors Variable in weight array"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/font/src/local/loader.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/font/local loader generated CSS Default CSS",
"next/font/local loader generated CSS Multiple styles default weight",
"next/font/local loader generated CSS Multiple weights default style",
"next/font/local loader generated CSS Other properties",
"next/font/local loader generated CSS Weight and style"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/font/src/local/pick-font-file-for-fallback-generation.test.ts": {
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pickFontFileForFallbackGeneration Invalid variable weight in array",
"pickFontFileForFallbackGeneration should error on invalid weight in array",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pickFontFileForFallbackGeneration should pick the thinner weight if both have the same distance to 400",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pickFontFileForFallbackGeneration should pick the weight closest to 400",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pickFontFileForFallbackGeneration should pick variable range closest to 400",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pickFontFileForFallbackGeneration should prefer normal style over italic"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/font/src/local/validate-local-font-function-call.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"validateLocalFontFunctionCall Empty src array",
"validateLocalFontFunctionCall Invalid declaration",
"validateLocalFontFunctionCall Invalid display value",
"validateLocalFontFunctionCall Invalid file extension",
"validateLocalFontFunctionCall Missing src",
"validateLocalFontFunctionCall Not using default export"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"packages/next/src/build/normalize-catchall-routes.test.ts": {
"passed": [
"normalizeCatchallRoutes should add the catch-all route to all matched paths at the root",
"normalizeCatchallRoutes should add the catch-all route to all matched paths when nested",
Update Turbopack test manifest (#60371) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-08 10:23:29 +01:00
"normalizeCatchallRoutes should not add the catch-all route to a path that has a @children slot",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"normalizeCatchallRoutes should not add the catch-all route to segments that have a more specific default",
"normalizeCatchallRoutes should not add the catch-all to the interception route"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"packages/next/src/build/webpack/loaders/metadata/resolve-route-data.test.ts": {
"passed": [
"resolveRouteData resolveRobots should error with ts when specify both wildcard userAgent and specific userAgent",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"resolveRouteData resolveRobots should resolve robots.txt",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"resolveRouteData resolveSitemap should resolve sitemap.xml"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/next/src/build/webpack/plugins/next-types-plugin/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next-types-plugin should generate correct base import path",
"next-types-plugin should generate correct base import path for custom projects",
"next-types-plugin should generate correct base import path for nx monorepos"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/next/src/client/components/navigation.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/navigation should be able to construct URLSearchParams from ReadonlyURLSearchParams"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/next/src/client/components/promise-queue.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"PromiseQueue should allow bumping a promise to be next in the queue",
"PromiseQueue should limit the number of concurrent promises"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/react-dev-overlay/internal/components/hot-linked-text/get-words-and-whitespaces.test.ts": {
"passed": [
"getWordsAndWhitespaces should return sequences of words and whitespaces"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/redirect.test.ts": {
"passed": ["test should throw a redirect error"],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/next/src/client/components/router-reducer/apply-router-state-patch-to-tree.test.tsx": {
"passed": ["applyRouterStatePatchToTree should apply a patch to the tree"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/next/src/client/components/router-reducer/compute-changed-path.test.ts": {
"passed": ["computeChangedPath should return the correct path"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/create-href-from-url.test.ts": {
"passed": [
"createHrefFromUrl adds hash",
"createHrefFromUrl adds pathname",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"createHrefFromUrl adds pathname, searchParams, and hash",
"createHrefFromUrl adds searchParams",
"createHrefFromUrl returns a string"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/create-initial-router-state.test.tsx": {
"passed": [
"createInitialRouterState should return the correct initial router state"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/create-router-cache-key.test.ts": {
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"createRouterCacheKey should support catch all segment",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"createRouterCacheKey should support dynamic segment",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"createRouterCacheKey should support string segment"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/next/src/client/components/router-reducer/fill-cache-with-data-property.test.tsx": {
"passed": ["fillCacheWithDataProperty should add data property"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/fill-cache-with-new-subtree-data.test.tsx": {
"passed": [
Rename CacheNode.subTreeData -> .rsc (#59491) I want to give this field a name that's bit less generic and distinguishes it from `lazyData` (because that one has a different type and is a special case we want to eventually remove). I'm also about to add an optional `prefetchRsc` field that represents a prefetched version of the same value. The common suffix is meant to communicate how they are related. Doing this rename in its own PR because it's a pure find-and-replace, whereas the later steps are not. Closes NEXT-1846
2023-12-12 03:41:03 +01:00
"fillCacheWithNewSubtreeData should apply rsc and head property"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/fill-lazy-items-till-leaf-with-head.test.tsx": {
"passed": [
"fillLazyItemsTillLeafWithHead should fill lazy items till leaf with head"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/get-segment-value.test.ts": {
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"getSegmentValue should support catch all segment",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"getSegmentValue should support dynamic segment",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"getSegmentValue should support string segment"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/invalidate-cache-below-flight-segmentpath.test.tsx": {
"passed": [
"invalidateCacheBelowFlightSegmentPath should invalidate cache below flight segment path"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/invalidate-cache-by-router-state.test.tsx": {
"passed": [
"invalidateCacheByRouterState should invalidate the cache by router state"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/is-navigating-to-new-root-layout.test.ts": {
"passed": [
"shouldHardNavigate should return false if there is no new root layout",
"shouldHardNavigate should return true if there is a mismatch between the root layouts"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/reducers/find-head-in-cache.test.tsx": {
"passed": ["findHeadInCache should find the head"],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/reducers/navigate-reducer.test.tsx": {
"passed": [
"navigateReducer should apply navigation",
"navigateReducer should apply navigation for external url (push)",
"navigateReducer should apply navigation for external url (replace)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"navigateReducer should apply navigation for hash fragments within a different tree",
"navigateReducer should apply navigation for hash fragments within the same tree",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"navigateReducer should apply navigation for scroll",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"navigateReducer should apply navigation when called twice (concurrent)",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"navigateReducer should apply navigation with prefetched data",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"navigateReducer should apply parallel routes navigation (concurrent)"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/reducers/prefetch-reducer.test.tsx": {
"passed": [
"prefetchReducer should apply navigation",
"prefetchReducer should apply navigation (concurrent)"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/reducers/refresh-reducer.test.tsx": {
"passed": [
"refreshReducer should apply refresh",
"refreshReducer should apply refresh (concurrent)",
"refreshReducer should invalidate all segments (concurrent)",
"refreshReducer should invalidate prefetchCache (concurrent)"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/reducers/restore-reducer.test.tsx": {
"passed": [
"serverPatchReducer should apply server patch",
"serverPatchReducer should apply server patch (concurrent)"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/reducers/server-patch-reducer.test.tsx": {
"passed": [
"serverPatchReducer should apply server patch",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"serverPatchReducer should apply server patch without affecting focusAndScrollRef",
"serverPatchReducer should gracefully recover if the server patch doesn't match the current tree"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/client/components/router-reducer/should-hard-navigate.test.tsx": {
"passed": [
"shouldHardNavigate should return false if segments are dynamic and match",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"shouldHardNavigate should return false if the segments match",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"shouldHardNavigate should return true if segments are dynamic and mismatch"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"packages/next/src/lib/batcher.test.ts": {
"passed": [
"Batcher batch should batch multiple calls to the same key",
"Batcher batch should execute the work function immediately",
"Batcher batch should not batch calls to different keys",
"Batcher batch should use the cacheKeyFn to generate cache keys",
"Batcher batch should use the schedulerFn to schedule work"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"packages/next/src/lib/format-server-error.test.ts": {
"passed": ["formatServerError should not append message several times"],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"packages/next/src/lib/metadata/resolve-metadata.test.ts": {
"passed": [
"accumulateMetadata alternate should support alternate descriptors",
"accumulateMetadata alternate should support string alternate",
"accumulateMetadata icon should resolve icons.apple",
"accumulateMetadata icon should resolve icons.icon correctly",
"accumulateMetadata itunes should resolve relative url starting with ./ with pathname for itunes.appArgument",
"accumulateMetadata openGraph and twitter should convert string or URL images field to array, not only for basic og type",
"accumulateMetadata openGraph and twitter should fill only the existing props from openGraph to twitter",
"accumulateMetadata openGraph and twitter should fill twitter with partial existing openGraph metadata",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"accumulateMetadata openGraph and twitter should inherit metadata title description into openGraph or twitter if they are configured",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"accumulateMetadata openGraph and twitter should override openGraph or twitter images when current layer specifies social images properties",
"accumulateMetadata openGraph and twitter should resolve relative url starting with ./ with pathname for openGraph.url",
"accumulateMetadata title should merge title with page title",
"accumulateMetadata title should merge title with parent layout ",
"accumulateMetadata typing should support both sync and async metadata",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"accumulateViewport themeColor should support string theme color",
"accumulateViewport themeColor should support theme color descriptors",
"accumulateViewport viewport should support viewport descriptors"
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"packages/next/src/lib/metadata/resolvers/resolve-opengraph.test.ts": {
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"resolveImages should filter out invalid images",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"resolveImages should not mutate passed images",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"resolveImages should resolve images"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/next/src/lib/metadata/resolvers/resolve-title.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"resolveTitle should resolve nullable template as empty string title",
"resolveTitle should resolve title with template"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/lib/metadata/resolvers/resolve-url.test.ts": {
"passed": [
"metadata: resolveUrl should compose with metadataBase when url is relative or absolute",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"metadata: resolveUrl should ignore metadataBase when url is valid URL",
"metadata: resolveUrl should return null when url is falsy",
"metadata: resolveUrl should return url itself when metadataBase is null or url is valid URL"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"packages/next/src/server/app-render/csrf-protection.test.ts": {
"passed": [
"isCsrfOriginAllowed should return false when allowedOrigins contains originDomain with non-matching pattern",
"isCsrfOriginAllowed should return false when allowedOrigins does not contain originDomain",
"isCsrfOriginAllowed should return false when allowedOrigins is empty",
"isCsrfOriginAllowed should return false when allowedOrigins is empty string",
"isCsrfOriginAllowed should return false when allowedOrigins is undefined",
"isCsrfOriginAllowed should return true when allowedOrigins contains originDomain",
"isCsrfOriginAllowed should return true when allowedOrigins contains originDomain with matching pattern"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"packages/next/src/server/app-render/types.test.ts": {
"passed": [
"flightRouterStateSchema should not validate an incorrect flight router state",
"flightRouterStateSchema should validate a correct flight router state"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"packages/next/src/server/config.test.ts": {
"passed": [
"loadConfig nextConfig.images defaults should assign a `images.remotePatterns` when using assetPrefix",
"loadConfig nextConfig.images defaults should not assign a duplicate `images.remotePatterns` value when using assetPrefix"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"packages/next/src/server/dev/parse-version-info.test.ts": {
"passed": [
"parse version info installed: 12.0.0, latest: 13.1.1, canary: 13.0.1-canary.0 yields stale-major",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"parse version info installed: 13.0.0, latest: 12.0.0, canary: 12.0.1-canary.0 yields newer-than-npm",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"parse version info installed: 13.0.0, latest: 13.1.0, canary: 13.1.1-canary.0 yields stale-minor",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"parse version info installed: 13.0.0, latest: 13.1.0, canary: invalid yields unknown",
"parse version info installed: 13.0.0, latest: invalid, canary: 13.0.1-canary.0 yields unknown",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"parse version info installed: 13.0.1-canary.0, latest: 13.0.0, canary: 13.0.1-canary.1 yields stale-prerelease",
"parse version info installed: 13.0.1-canary.0, latest: 13.0.0, canary: 13.1.0-canary.0 yields stale-prerelease",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"parse version info installed: 13.0.1-canary.8, latest: 13.0.0, canary: 13.0.1-canary.7 yields newer-than-npm",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"parse version info installed: 13.1.0, latest: 13.1.0, canary: 13.1.1-canary.0 yields fresh",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"parse version info installed: 13.1.1, latest: 13.1.2, canary: 13.1.3-canary.0 yields stale-patch",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"parse version info installed: 13.1.1-canary.7, latest: 13.1.0, canary: 13.1.1-canary.7 yields fresh",
"parse version info installed: invalid, latest: 13.0.1, canary: 13.0.1-canary.0 yields unknown"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/next/src/server/future/helpers/i18n-provider.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
"I18NProvider analyze for pathname / and defaultLocale en",
"I18NProvider analyze for pathname /another/page and defaultLocale en",
"I18NProvider analyze for pathname /en and defaultLocale en",
"I18NProvider analyze for pathname /en-CA and defaultLocale en",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"I18NProvider analyze for pathname /en-CA/another/page and defaultLocale en",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"I18NProvider analyze for pathname /en/another/page and defaultLocale en",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"I18NProvider analyze for pathname /fr and defaultLocale en",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"I18NProvider analyze for pathname /fr/another/page and defaultLocale en",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"I18NProvider detectDomainLocale for domain example.ca",
"I18NProvider detectDomainLocale for domain example.com",
"I18NProvider detectDomainLocale for domain example.de",
"I18NProvider detectDomainLocale for domain example.fr",
"I18NProvider should detect the correct domain locale"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"packages/next/src/server/future/helpers/interception-routes.test.ts": {
"passed": [
"Interception Route helper extractInterceptionRouteInformation should check the segment length",
"Interception Route helper extractInterceptionRouteInformation should extract correct information",
"Interception Route helper extractInterceptionRouteInformation should not extract incorrect information",
"Interception Route helper isInterceptionRouteAppPath should not validate incorrect paths",
"Interception Route helper isInterceptionRouteAppPath should validate correct paths"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/server/future/normalizers/absolute-filename-normalizer.test.ts": {
"passed": [
"AbsoluteFilenameNormalizer normalizes '<root>/app/basic/(grouped)/endpoint/nested/route.ts' to '/basic/(grouped)/endpoint/nested/route'",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"AbsoluteFilenameNormalizer normalizes '<root>/pages/basic/endpoint/index.ts' to '/basic/endpoint'",
"AbsoluteFilenameNormalizer normalizes '<root>/pages/basic/endpoint/nested.ts' to '/basic/endpoint/nested'"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"packages/next/src/server/future/normalizers/request/base-path.test.ts": {
"passed": [
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"BasePathPathnameNormalizer should throw when provided with a basePath of \"/\"",
"BasePathPathnameNormalizer should throw when provided with a blank basePath"
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"packages/next/src/server/future/normalizers/request/next-data.test.ts": {
"passed": [
"NextDataPathnameNormalizer constructor should error when no buildID is provided",
"NextDataPathnameNormalizer match should return false if the pathname does not start with the prefix",
"NextDataPathnameNormalizer match should return false if the pathname only ends with `.json`",
"NextDataPathnameNormalizer match should return true if it matches",
"NextDataPathnameNormalizer normalize should normalize `/index` to `/`",
"NextDataPathnameNormalizer normalize should return the same pathname if we are not matched and the pathname does not start with the prefix",
"NextDataPathnameNormalizer normalize should strip the prefix and the `.json` extension from the pathname when it matches"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"packages/next/src/server/future/normalizers/request/postponed.test.ts": {
"passed": [
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"PostponedPathnameNormalizer match should match",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"PostponedPathnameNormalizer match should not match for other pathnames",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"PostponedPathnameNormalizer normalize should normalize `/index` to `/`",
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"PostponedPathnameNormalizer normalize should normalize when matched",
"PostponedPathnameNormalizer normalize should not normalize but not matched"
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"packages/next/src/server/future/normalizers/request/prefix.test.ts": {
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"passed": [
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"PrefixPathnameNormalizer match should return false if the pathname does not start with the prefix",
"PrefixPathnameNormalizer match should return true if the pathname starts with the prefix",
"PrefixPathnameNormalizer normalize should return the same pathname if we are not matched and the pathname does not start with the prefix",
"PrefixPathnameNormalizer normalize should strip the prefix from the pathname when it matches",
"PrefixPathnameNormalizer should throw if the prefix ends with a slash"
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"packages/next/src/server/future/normalizers/request/suffix.test.ts": {
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"passed": [
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"SuffixPathnameNormalizer match should return false if the pathname does not end with `.rsc`",
"SuffixPathnameNormalizer match should return true if it matches",
"SuffixPathnameNormalizer normalize should return the same pathname if we are not matched and the pathname does not end with `.rsc`",
"SuffixPathnameNormalizer normalize should strip the `.rsc` extension from the pathname when it matches"
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"packages/next/src/server/future/route-matcher-managers/default-route-matcher-manager.test.ts": {
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"DefaultRouteMatcherManager calls the locale route matcher when one is provided",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"DefaultRouteMatcherManager can handle locale aware matchers for /en-US/some/path and locale en-US",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"DefaultRouteMatcherManager can handle locale aware matchers for /nl-NL/some/path and locale nl-NL",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"DefaultRouteMatcherManager can handle locale aware matchers for /some/path and locale {\"inferredFromDefault\": false, \"pathname\": \"/some/path\"}",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"DefaultRouteMatcherManager will match a route that is not locale aware when it was inferred from the default locale",
"DefaultRouteMatcherManager will not error and not match when no matchers are provided",
"DefaultRouteMatcherManager will throw an error when used before it has been reloaded"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/next/src/server/future/route-matcher-providers/app-page-route-matcher-provider.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"AppPageRouteMatcherProvider manifest matching returns the correct routes for /",
"AppPageRouteMatcherProvider manifest matching returns the correct routes for /about",
"AppPageRouteMatcherProvider manifest matching returns the correct routes for /dashboard/users",
"AppPageRouteMatcherProvider manifest matching returns the correct routes for /dashboard/users/[id]",
"AppPageRouteMatcherProvider returns no routes with an empty manifest"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/next/src/server/future/route-matcher-providers/app-route-route-matcher-provider.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"AppRouteRouteMatcherProvider manifest matching returns the correct routes for /",
"AppRouteRouteMatcherProvider manifest matching returns the correct routes for /users",
"AppRouteRouteMatcherProvider manifest matching returns the correct routes for /users/[id]",
"AppRouteRouteMatcherProvider returns no routes with an empty manifest"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/server/future/route-matcher-providers/dev/dev-app-page-route-matcher-provider.test.ts": {
"passed": [
"DevAppPageRouteMatcher filename matching matches the '/(marketing)/about/page' route specified with the provided files",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"DevAppPageRouteMatcher filename matching matches the '/page' route specified with the provided files",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"DevAppPageRouteMatcher filename matching matches the '/some/other/page' route specified with the provided files",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"DevAppPageRouteMatcher returns no routes with an empty filesystem"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/server/future/route-matcher-providers/dev/dev-app-route-route-matcher-provider.test.ts": {
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"DevAppRouteRouteMatcher filename matching matches the '/route' route specified with the provided files",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"DevAppRouteRouteMatcher filename matching matches the '/some/other/route' route specified with the provided files",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"DevAppRouteRouteMatcher returns no routes with an empty filesystem"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/server/future/route-matcher-providers/dev/dev-pages-api-route-matcher-provider.test.ts": {
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"DevPagesAPIRouteMatcherProvider filename matching matches the '/api' route specified with the provided files",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"DevPagesAPIRouteMatcherProvider filename matching matches the '/api/other' route specified with the provided files",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"DevPagesAPIRouteMatcherProvider filename matching matches the '/api/other/route' route specified with the provided files",
"DevPagesAPIRouteMatcherProvider returns no routes with an empty filesystem"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/server/future/route-matcher-providers/dev/dev-pages-route-matcher-provider.test.ts": {
"passed": [
"DevPagesRouteMatcherProvider filename matching matches the '/' route specified with the provided files",
"DevPagesRouteMatcherProvider filename matching matches the '/some/api/route' route specified with the provided files",
"DevPagesRouteMatcherProvider filename matching matches the '/some/other/route' route specified with the provided files",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"DevPagesRouteMatcherProvider filename matching matches the '/some/other/route/index/route' route specified with the provided files",
"DevPagesRouteMatcherProvider returns no routes with an empty filesystem"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/next/src/server/future/route-matcher-providers/dev/helpers/file-reader/batched-file-reader.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"CachedFileReader will only scan the filesystem a minimal amount of times",
"CachedFileReader will send an error back only to the correct reader"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/next/src/server/future/route-matcher-providers/pages-api-route-matcher-provider.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"PagesAPIRouteMatcherProvider manifest matching returns the correct routes for /api",
"PagesAPIRouteMatcherProvider manifest matching returns the correct routes for /api/users",
"PagesAPIRouteMatcherProvider manifest matching returns the correct routes for /api/users/[id]",
"PagesAPIRouteMatcherProvider returns no routes with an empty manifest"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/server/future/route-matcher-providers/pages-route-matcher-provider.test.ts": {
"passed": [
"PagesRouteMatcherProvider locale matching locale has the match for /",
"PagesRouteMatcherProvider locale matching locale has the match for /404",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"PagesRouteMatcherProvider locale matching locale has the match for /blog/[slug]",
"PagesRouteMatcherProvider manifest matching returns the correct routes for /",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"PagesRouteMatcherProvider manifest matching returns the correct routes for /users",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"PagesRouteMatcherProvider manifest matching returns the correct routes for /users/[id]",
"PagesRouteMatcherProvider returns no routes with an empty manifest"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/server/lib/mock-request.test.ts": {
"passed": [
"MockedRequest should have the correct properties",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"MockedResponse should handle set-cookie headers correctly",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"MockedResponse should merge headers correctly when calling writeHead",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"MockedResponse should update the statusMessage after calling writeHead"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/next/src/server/node-polyfill-crypto.test.ts": {
"passed": ["node-polyfill-crypto overwrite crypto"],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"packages/next/src/server/web/spec-extension/adapters/headers.test.ts": {
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"HeadersAdapter case-insensitive should handle different case for header names",
"HeadersAdapter case-insensitive should handle different case for header names when mutated out of band",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"HeadersAdapter entries should return an iterator of entries",
"HeadersAdapter forEach should iterate over all entries",
"HeadersAdapter iterator should iterate over all entries",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"HeadersAdapter keys should return an iterator of keys",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"HeadersAdapter sealed should be able to seal a Headers instance",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"HeadersAdapter sealed should be able to seal a HeadersAdapter and still mutate the original",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"HeadersAdapter sealed should be able to seal a HeadersAdapter instance",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"HeadersAdapter should be able to create a new instance from a Headers",
"HeadersAdapter should be able to create a new instance from a HeadersAdapter",
"HeadersAdapter should be able to create a new instance from an IncomingHttpHeaders",
"HeadersAdapter should be able to create a new instance from an object",
"HeadersAdapter should handle multiple values for a header",
"HeadersAdapter values should return an iterator of values"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/server/web/spec-extension/adapters/request-cookies.test.ts": {
"passed": [
"RequestCookiesAdapter should be able to create a new instance from a RequestCookies",
"RequestCookiesAdapter should be able to create a new instance from an empty RequestCookies"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/server/web/utils.test.ts": {
"passed": [
"toNodeHeaders should handle a single set-cookie header correctly",
"toNodeHeaders should handle a single set-cookie header with multiple cookies correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"toNodeHeaders should handle mixed case set-cookie headers correctly",
"toNodeHeaders should handle multiple set-cookie headers correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/shared/lib/get-hostname.test.ts": {
"passed": [
"getHostname from URL should return 127.0.0.1 for http://127.0.0.1",
"getHostname from URL should return 127.0.0.1 for http://127.0.0.1/",
"getHostname from URL should return 127.0.0.1 for http://127.0.0.1:3000",
"getHostname from URL should return 8.8.8.8 for http://8.8.8.8",
"getHostname from URL should return 8.8.8.8 for http://8.8.8.8/",
"getHostname from URL should return 8.8.8.8 for http://8.8.8.8:3000",
"getHostname from URL should return example.com for http://example.com",
"getHostname from URL should return example.com for http://example.com/",
"getHostname from URL should return example.com for http://example.com:3000",
"getHostname from URL should return example.com for https://example.com",
"getHostname from URL should return example.com for https://example.com/",
"getHostname from URL should return example.com for https://example.com:3000",
"getHostname from URL should return localhost for http://localhost",
"getHostname from URL should return localhost for http://localhost/",
"getHostname from URL should return localhost for http://localhost:3000",
"getHostname should return undefined for empty input"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/next/src/shared/lib/router/adapters.test.tsx": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"adaptForAppRouterInstance should forward a call to `back()`",
"adaptForAppRouterInstance should forward a call to `forward()`",
"adaptForAppRouterInstance should forward a call to `prefetch()`",
"adaptForAppRouterInstance should forward a call to `push()`",
"adaptForAppRouterInstance should forward a call to `push()` with options",
"adaptForAppRouterInstance should forward a call to `reload()`",
"adaptForAppRouterInstance should forward a call to `replace()`",
"adaptForAppRouterInstance should forward a call to `replace()` with options"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"packages/next/src/shared/lib/router/utils/app-paths.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"normalizeRscPath should normalize url with .rsc",
"normalizeRscPath should normalize url with .rsc and searchparams"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"packages/next/src/shared/lib/router/utils/route-regex.test.ts": {
"passed": [
"getNamedRouteRegex should handle interception markers adjacent to dynamic path segments",
"getNamedRouteRegex should handle interception markers not adjacent to dynamic path segments",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"getNamedRouteRegex should handle multi-level interception markers",
"getNamedRouteRegex should handle optional catch-all dynamic path segments",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"getNamedRouteRegex should handle optional dynamic path segments",
"getNamedRouteRegex should match named routes correctly when interception markers are adjacent to dynamic segments"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"packages/next/src/trace/report/index.test.ts": {
"passed": [
"Trace Reporter JSON reporter should write the trace events to JSON file",
"Trace Reporter Telemetry reporter should record telemetry event"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"packages/next/src/trace/trace.test.ts": {
"passed": [
"Trace Tracer traces a block of code",
"Trace Worker correctly reports trace data from multiple workers",
"Trace Worker exports and initializes trace state",
"Trace Worker trace data is serializable to a worker"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance-app/ReactRefresh.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefresh app can edit a component without losing state",
"ReactRefresh app cyclic dependencies"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance-app/ReactRefreshLogBox-builtins.test.ts": {
Turbopack: Align some "Module not found" errors with webpack (#58518) This: - Sends an hmr sync event so that errors that occur after the initial hmr connection are sent to the client - Aligns on `path/to/file.js:line:column` format across error overlay implementations in the cli and on the web - Adapts "Module not found" errors from Turbopack to include Next.js-relevant formatting and documentation links to align with webpack Test Plan: Passes 3 tests that were previously failing Closes PACK-1974 --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by: Leah <github.leah@hrmny.sh> Co-authored-by: Zack Tanner <zacktanner@gmail.com>
2023-11-30 17:34:56 +01:00
"passed": [
"ReactRefreshLogBox app turbo Module not found empty import trace",
"ReactRefreshLogBox app turbo Module not found missing global CSS"
],
Move ReactRefreshLogBox-builtins tests to inline snapshots (#57952) This avoids separate snapshots for both Turbopack and Webpack, and correctly reflects that these fail.
2023-11-02 22:32:52 +01:00
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox app turbo Module not found",
"ReactRefreshLogBox app turbo Node.js builtins"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [
"ReactRefreshLogBox app default Module not found",
"ReactRefreshLogBox app default Module not found empty import trace",
"ReactRefreshLogBox app default Module not found missing global CSS",
"ReactRefreshLogBox app default Node.js builtins"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: Align some "Module not found" errors with webpack (#58518) This: - Sends an hmr sync event so that errors that occur after the initial hmr connection are sent to the client - Aligns on `path/to/file.js:line:column` format across error overlay implementations in the cli and on the web - Adapts "Module not found" errors from Turbopack to include Next.js-relevant formatting and documentation links to align with webpack Test Plan: Passes 3 tests that were previously failing Closes PACK-1974 --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by: Leah <github.leah@hrmny.sh> Co-authored-by: Zack Tanner <zacktanner@gmail.com>
2023-11-30 17:34:56 +01:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance-app/ReactRefreshLogBox-scss.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": ["ReactRefreshLogBox app scss syntax errors"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance-app/ReactRefreshLogBox.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"ReactRefreshLogBox app turbo Call stack count is correct for client error",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox app turbo Can't resolve @import in CSS file",
"ReactRefreshLogBox app turbo Import trace when module not found in layout",
"ReactRefreshLogBox app turbo Server component errors should open up in fullscreen",
"ReactRefreshLogBox app turbo Should not show __webpack_exports__ when exporting anonymous arrow function",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"ReactRefreshLogBox app turbo Unhandled errors and rejections opens up in the minimized state",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox app turbo boundaries",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"ReactRefreshLogBox app turbo client component can recover from error thrown in the module",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"ReactRefreshLogBox app turbo logbox: anchors links in error messages",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"ReactRefreshLogBox app turbo module init error not shown",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox app turbo server component can recover from error thrown in the module",
"ReactRefreshLogBox app turbo should strip whitespace correctly with newline"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox app turbo Call stack count is correct for server error",
"ReactRefreshLogBox app turbo conversion to class component (1)",
"ReactRefreshLogBox app turbo css syntax errors",
"ReactRefreshLogBox app turbo unterminated JSX"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [
"ReactRefreshLogBox app default Call stack count is correct for client error",
"ReactRefreshLogBox app default Call stack count is correct for server error",
"ReactRefreshLogBox app default Can't resolve @import in CSS file",
"ReactRefreshLogBox app default Import trace when module not found in layout",
"ReactRefreshLogBox app default Server component errors should open up in fullscreen",
"ReactRefreshLogBox app default Should not show __webpack_exports__ when exporting anonymous arrow function",
"ReactRefreshLogBox app default Unhandled errors and rejections opens up in the minimized state",
"ReactRefreshLogBox app default boundaries",
"ReactRefreshLogBox app default client component can recover from error thrown in the module",
"ReactRefreshLogBox app default conversion to class component (1)",
"ReactRefreshLogBox app default css syntax errors",
"ReactRefreshLogBox app default internal package errors",
"ReactRefreshLogBox app default logbox: anchors links in error messages",
"ReactRefreshLogBox app default module init error not shown",
"ReactRefreshLogBox app default non-Error errors are handled properly",
"ReactRefreshLogBox app default server component can recover from error thrown in the module",
"ReactRefreshLogBox app default should strip whitespace correctly with newline",
"ReactRefreshLogBox app default unterminated JSX",
"ReactRefreshLogBox app turbo internal package errors",
"ReactRefreshLogBox app turbo non-Error errors are handled properly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/development/acceptance-app/ReactRefreshLogBoxMisc.test.ts": {
"passed": [],
"failed": [],
"pending": [
"ReactRefreshLogBox app <Link> component props errors",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox app <Link> with multiple children",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"ReactRefreshLogBox app server-side only compilation errors"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/development/acceptance-app/ReactRefreshModule.test.ts": {
"passed": [],
"failed": ["ReactRefreshModule app should allow any variable names"],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance-app/ReactRefreshRegression.test.ts": {
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"passed": [
"ReactRefreshRegression app can fast refresh a page with static generation"
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [
"ReactRefreshRegression app custom loader mdx should have Fast Refresh enabled",
"ReactRefreshRegression app shows an overlay for anonymous function server-side error",
"ReactRefreshRegression app shows an overlay for server-side error in client component",
"ReactRefreshRegression app shows an overlay for server-side error in server component"
],
"pending": [
"ReactRefreshRegression app styled-components hydration mismatch"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"flakey": [
"ReactRefreshRegression app can fast refresh a page with config",
"ReactRefreshRegression app can fast refresh a page with dynamic rendering"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"runtimeError": false
},
"test/development/acceptance-app/ReactRefreshRequire.test.ts": {
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"passed": [
"ReactRefreshRequire app bails out if the update bubbles to the root via one of the paths",
"ReactRefreshRequire app bails out if update bubbles to the root via the only path",
"ReactRefreshRequire app can continue hot updates after module-level errors with ES6 exports",
"ReactRefreshRequire app can continue hot updates after module-level errors with module.exports",
"ReactRefreshRequire app can replace a module before it is loaded",
"ReactRefreshRequire app does not accumulate stale exports over time",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"ReactRefreshRequire app provides fresh value for ES6 default import in parents",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"ReactRefreshRequire app provides fresh value for ES6 named import in parents",
"ReactRefreshRequire app provides fresh value for exports.* in parents",
"ReactRefreshRequire app provides fresh value for module.exports in parents",
"ReactRefreshRequire app runs dependencies before dependents",
"ReactRefreshRequire app stops update propagation after module-level errors"
],
"failed": [],
"pending": [
"ReactRefreshRequire app propagates a module that stops accepting in next version"
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
],
Turbopack: Chunking Refactoring (#56756) ### What? see https://github.com/vercel/turbo/pull/6160 ### Turbopack Changes * https://github.com/vercel/turbo/pull/6116 * https://github.com/vercel/turbo/pull/6140 * https://github.com/vercel/turbo/pull/6118 * https://github.com/vercel/turbo/pull/6128 * https://github.com/vercel/turbo/pull/6129 * https://github.com/vercel/turbo/pull/6160 Closes WEB-1772 Co-authored-by: Justin Ridgewell <112982+jridgewell@users.noreply.github.com>
2023-10-13 13:44:44 +02:00
"flakey": [
"ReactRefreshRequire app propagates a hot update to closest accepted module",
"ReactRefreshRequire app propagates hot update to all inverse dependencies",
"ReactRefreshRequire app re-runs accepted modules"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance-app/app-hmr-changes.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Error overlay - RSC build errors should handle successive HMR changes with errors correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance-app/component-stack.test.ts": {
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Component Stack in error overlay should show a component stack on hydration error"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance-app/dynamic-error.test.ts": {
"passed": [
"dynamic = \"error\" in devmode should show error overlay when dynamic is forced"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance-app/editor-links.test.ts": {
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"passed": [
"Error overlay - editor links should be possible to open source file on build error"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Error overlay - editor links should be possible to open import trace files on RSC parse error",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"Error overlay - editor links should be possible to open import trace files on module not found error"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance-app/error-message-url.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Error overlay - error message urls should be possible to click url in runtime error"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Error overlay - error message urls should be possible to click url in build error"
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/development/acceptance-app/error-recovery.test.ts": {
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"passed": [
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"Error recovery app turbo can recover from a syntax error without losing state",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"Error recovery app turbo client component can recover from a component error",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"Error recovery app turbo render error not shown right after syntax error",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"Error recovery app turbo stuck error"
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [
"Error recovery app turbo can recover from a event handler error",
"Error recovery app turbo client component can recover from syntax error",
"Error recovery app turbo displays build error on initial page load",
"Error recovery app turbo server component can recover from a component error",
"Error recovery app turbo server component can recover from syntax error",
"Error recovery app turbo syntax > runtime error"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Error recovery app default can recover from a event handler error",
"Error recovery app default can recover from a syntax error without losing state",
"Error recovery app default client component can recover from a component error",
"Error recovery app default client component can recover from syntax error",
"Error recovery app default displays build error on initial page load",
"Error recovery app default render error not shown right after syntax error",
"Error recovery app default server component can recover from a component error",
"Error recovery app default server component can recover from syntax error",
"Error recovery app default stuck error",
"Error recovery app default syntax > runtime error"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance-app/hydration-error.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Error overlay for hydration errors should not show a hydration error when using `useId` in a client component",
"Error overlay for hydration errors should show correct hydration error when client and server render different text",
"Error overlay for hydration errors should show correct hydration error when client renders an extra element",
"Error overlay for hydration errors should show correct hydration error when client renders an extra node inside Suspense content",
"Error overlay for hydration errors should show correct hydration error when client renders an extra text node",
"Error overlay for hydration errors should show correct hydration error when server renders an extra element",
"Error overlay for hydration errors should show correct hydration error when server renders an extra text node"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance-app/invalid-imports.test.ts": {
"passed": [],
"failed": [
"Error Overlay invalid imports should show error when external package imports client-only in server component",
"Error Overlay invalid imports should show error when external package imports server-only in client component",
"Error Overlay invalid imports should show error when using styled-jsx in server component"
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/development/acceptance-app/rsc-build-errors.test.ts": {
"passed": [
"Error overlay - RSC build errors should allow to use and handle rsc poisoning client-only",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"Error overlay - RSC build errors should error for invalid undefined module retuning from next dynamic",
Fix useOptimistic in server components bug. Add tests for invalid React server APIs (#59621) ## What? Fixes a bug where `useOptimistic` wouldn't trigger a compiler error when imported in Server Components. Adds tests for the following `import { x } from 'react'` in Server Components, where `x` is the value: - Component - createContext - createFactory - PureComponent - useDeferredValue - useEffect - useImperativeHandle - useInsertionEffect - useLayoutEffect - useReducer - useRef - useState - useSyncExternalStore - useTransition - useOptimistic These show a particular error explaining how to add `"use client"`: ![CleanShot 2023-12-14 at 14 49 37@2x](https://github.com/vercel/next.js/assets/6324199/e47eab71-b2a2-4c14-bec0-0d5cdd720e80) <!-- Thanks for opening a PR! Your contribution is much appreciated.i: To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-12-14 21:09:41 +01:00
"Error overlay - RSC build errors should error when Component from react is used in server component",
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"Error overlay - RSC build errors should error when PureComponent from react is used in server component",
Fix useOptimistic in server components bug. Add tests for invalid React server APIs (#59621) ## What? Fixes a bug where `useOptimistic` wouldn't trigger a compiler error when imported in Server Components. Adds tests for the following `import { x } from 'react'` in Server Components, where `x` is the value: - Component - createContext - createFactory - PureComponent - useDeferredValue - useEffect - useImperativeHandle - useInsertionEffect - useLayoutEffect - useReducer - useRef - useState - useSyncExternalStore - useTransition - useOptimistic These show a particular error explaining how to add `"use client"`: ![CleanShot 2023-12-14 at 14 49 37@2x](https://github.com/vercel/next.js/assets/6324199/e47eab71-b2a2-4c14-bec0-0d5cdd720e80) <!-- Thanks for opening a PR! Your contribution is much appreciated.i: To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-12-14 21:09:41 +01:00
"Error overlay - RSC build errors should error when createContext from react is used in server component",
"Error overlay - RSC build errors should error when createFactory from react is used in server component",
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"Error overlay - RSC build errors should error when findDOMNode from react-dom is used in server component",
"Error overlay - RSC build errors should error when flushSync from react-dom is used in server component",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"Error overlay - RSC build errors should error when page component export is not valid",
"Error overlay - RSC build errors should error when page component export is not valid on initial load",
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"Error overlay - RSC build errors should error when unstable_batchedUpdates from react-dom is used in server component",
Fix useOptimistic in server components bug. Add tests for invalid React server APIs (#59621) ## What? Fixes a bug where `useOptimistic` wouldn't trigger a compiler error when imported in Server Components. Adds tests for the following `import { x } from 'react'` in Server Components, where `x` is the value: - Component - createContext - createFactory - PureComponent - useDeferredValue - useEffect - useImperativeHandle - useInsertionEffect - useLayoutEffect - useReducer - useRef - useState - useSyncExternalStore - useTransition - useOptimistic These show a particular error explaining how to add `"use client"`: ![CleanShot 2023-12-14 at 14 49 37@2x](https://github.com/vercel/next.js/assets/6324199/e47eab71-b2a2-4c14-bec0-0d5cdd720e80) <!-- Thanks for opening a PR! Your contribution is much appreciated.i: To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-12-14 21:09:41 +01:00
"Error overlay - RSC build errors should error when useDeferredValue from react is used in server component",
"Error overlay - RSC build errors should error when useEffect from react is used in server component",
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"Error overlay - RSC build errors should error when useFormState from react-dom is used in server component",
"Error overlay - RSC build errors should error when useFormStatus from react-dom is used in server component",
Fix useOptimistic in server components bug. Add tests for invalid React server APIs (#59621) ## What? Fixes a bug where `useOptimistic` wouldn't trigger a compiler error when imported in Server Components. Adds tests for the following `import { x } from 'react'` in Server Components, where `x` is the value: - Component - createContext - createFactory - PureComponent - useDeferredValue - useEffect - useImperativeHandle - useInsertionEffect - useLayoutEffect - useReducer - useRef - useState - useSyncExternalStore - useTransition - useOptimistic These show a particular error explaining how to add `"use client"`: ![CleanShot 2023-12-14 at 14 49 37@2x](https://github.com/vercel/next.js/assets/6324199/e47eab71-b2a2-4c14-bec0-0d5cdd720e80) <!-- Thanks for opening a PR! Your contribution is much appreciated.i: To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-12-14 21:09:41 +01:00
"Error overlay - RSC build errors should error when useImperativeHandle from react is used in server component",
"Error overlay - RSC build errors should error when useInsertionEffect from react is used in server component",
"Error overlay - RSC build errors should error when useLayoutEffect from react is used in server component",
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"Error overlay - RSC build errors should error when useOptimistic from react is used in server component",
Fix useOptimistic in server components bug. Add tests for invalid React server APIs (#59621) ## What? Fixes a bug where `useOptimistic` wouldn't trigger a compiler error when imported in Server Components. Adds tests for the following `import { x } from 'react'` in Server Components, where `x` is the value: - Component - createContext - createFactory - PureComponent - useDeferredValue - useEffect - useImperativeHandle - useInsertionEffect - useLayoutEffect - useReducer - useRef - useState - useSyncExternalStore - useTransition - useOptimistic These show a particular error explaining how to add `"use client"`: ![CleanShot 2023-12-14 at 14 49 37@2x](https://github.com/vercel/next.js/assets/6324199/e47eab71-b2a2-4c14-bec0-0d5cdd720e80) <!-- Thanks for opening a PR! Your contribution is much appreciated.i: To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-12-14 21:09:41 +01:00
"Error overlay - RSC build errors should error when useReducer from react is used in server component",
"Error overlay - RSC build errors should error when useRef from react is used in server component",
"Error overlay - RSC build errors should error when useState from react is used in server component",
"Error overlay - RSC build errors should error when useSyncExternalStore from react is used in server component",
"Error overlay - RSC build errors should error when useTransition from react is used in server component",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"Error overlay - RSC build errors should freeze parent resolved metadata to avoid mutating in generateMetadata",
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"Error overlay - RSC build errors should throw an error when \"Component\" is imported in server components",
feat(next-core): apply rsc transform in turbopack (#59629) ### What? Turbopack does not apply same transform for the react server components, which makes missing lot of compilation error validation and custom comments. PR refactors transform to be used in next-swc / turbopack both, then apply it into turbopack. There are still some of test cases are not passing, might need further digging for the transform condition. Closes PACK-2155 --------- Co-authored-by: Tim Neutkens <tim@timneutkens.nl>
2024-01-05 16:14:06 +01:00
"Error overlay - RSC build errors should throw an error when \"use client\" is on the top level but after other expressions"
],
"failed": [
"Error overlay - RSC build errors should allow to use and handle rsc poisoning server-only",
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"Error overlay - RSC build errors should throw an error when error file is a server component",
"Error overlay - RSC build errors should throw an error when error file is a server component with empty error file",
"Error overlay - RSC build errors should throw an error when getServerSideProps is used",
"Error overlay - RSC build errors should throw an error when metadata export is used in client components",
"Error overlay - RSC build errors should throw an error when metadata exports are used together in server components"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
"pending": [
"Error overlay - RSC build errors should throw an error when getStaticProps is used"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"test/development/acceptance-app/rsc-runtime-errors.test.ts": {
"passed": [
"Error overlay - RSC runtime errors should show runtime errors if invalid client API from node_modules is executed",
"Error overlay - RSC runtime errors should show runtime errors if invalid server API from node_modules is executed"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"test/development/acceptance-app/server-components.test.ts": {
"passed": [
"Error Overlay for server components Class component used in Server Component should show error when Class Component is used",
"Error Overlay for server components Class component used in Server Component should show error when Component is rendered in external package",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Error Overlay for server components Class component used in Server Component should show error when React.PureComponent is rendered in external package",
"Error Overlay for server components Next.js component hooks called in Server Component should show error when usePathname is called",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Error Overlay for server components Next.js component hooks called in Server Component should show error when useRouter is called",
"Error Overlay for server components Next.js component hooks called in Server Component should show error when useSearchParams is called",
"Error Overlay for server components Next.js component hooks called in Server Component should show error when useSelectedLayoutSegment is called",
"Error Overlay for server components Next.js component hooks called in Server Component should show error when useSelectedLayoutSegments is called",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Error Overlay for server components React component hooks called in Server Component should show error when React client hook is called in external package",
"Error Overlay for server components React component hooks called in Server Component should show error when React.<client-hook> is called",
"Error Overlay for server components React component hooks called in Server Component should show error when React.<client-hook> is called in external package",
"Error Overlay for server components React component hooks called in Server Component should show error when React.experiment_useOptimistic is called",
"Error Overlay for server components React component hooks called in Server Component should show error when React.experiment_useOptimistic is renamed in destructuring",
"Error Overlay for server components createContext called in Server Component should show error when React.createContext is called",
"Error Overlay for server components createContext called in Server Component should show error when React.createContext is called in external package",
"Error Overlay for server components createContext called in Server Component should show error when createContext is called in external package"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance-app/version-staleness.test.ts": {
"passed": [],
"failed": [],
"pending": [
"Error Overlay version staleness should show version staleness in build error",
"Error Overlay version staleness should show version staleness in render error",
"Error Overlay version staleness should show version staleness in runtime error"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"test/development/acceptance/ReactRefresh.test.ts": {
"passed": [
"ReactRefresh can edit a component without losing state",
"ReactRefresh cyclic dependencies"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/development/acceptance/ReactRefreshLogBox-app-doc.test.ts": {
"passed": [
"ReactRefreshLogBox turbo empty _app shows logbox",
"ReactRefreshLogBox turbo empty _document shows logbox"
],
"failed": [
"ReactRefreshLogBox turbo _app syntax error shows logbox",
"ReactRefreshLogBox turbo _document syntax error shows logbox"
],
"pending": [
"ReactRefreshLogBox default _app syntax error shows logbox",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox default _document syntax error shows logbox",
"ReactRefreshLogBox default empty _app shows logbox",
"ReactRefreshLogBox default empty _document shows logbox"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance/ReactRefreshLogBox-builtins.test.ts": {
Turbopack: Align some "Module not found" errors with webpack (#58518) This: - Sends an hmr sync event so that errors that occur after the initial hmr connection are sent to the client - Aligns on `path/to/file.js:line:column` format across error overlay implementations in the cli and on the web - Adapts "Module not found" errors from Turbopack to include Next.js-relevant formatting and documentation links to align with webpack Test Plan: Passes 3 tests that were previously failing Closes PACK-1974 --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by: Leah <github.leah@hrmny.sh> Co-authored-by: Zack Tanner <zacktanner@gmail.com>
2023-11-30 17:34:56 +01:00
"passed": [
"ReactRefreshLogBox turbo Module not found (empty import trace)"
],
Move ReactRefreshLogBox-builtins tests to inline snapshots (#57952) This avoids separate snapshots for both Turbopack and Webpack, and correctly reflects that these fail.
2023-11-02 22:32:52 +01:00
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox turbo Module not found",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"ReactRefreshLogBox turbo Module not found (missing global CSS)",
"ReactRefreshLogBox turbo Node.js builtins"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox default Module not found",
"ReactRefreshLogBox default Module not found (empty import trace)",
"ReactRefreshLogBox default Module not found (missing global CSS)",
"ReactRefreshLogBox default Node.js builtins"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance/ReactRefreshLogBox-scss.test.ts": {
"passed": [],
"failed": [],
"pending": ["ReactRefreshLogBox scss syntax errors"],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/development/acceptance/ReactRefreshLogBox.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox turbo boundaries",
Update Turbopack test manifest (#60413) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-09 10:32:10 +01:00
"ReactRefreshLogBox turbo logbox: anchors links in error messages",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox turbo module init error not shown",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"ReactRefreshLogBox turbo non-Error errors are handled properly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox turbo should strip whitespace correctly with newline"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox turbo css syntax errors",
"ReactRefreshLogBox turbo unterminated JSX"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox default boundaries",
"ReactRefreshLogBox default conversion to class component (1)",
"ReactRefreshLogBox default css syntax errors",
"ReactRefreshLogBox default internal package errors",
"ReactRefreshLogBox default logbox: anchors links in error messages",
"ReactRefreshLogBox default module init error not shown",
"ReactRefreshLogBox default non-Error errors are handled properly",
"ReactRefreshLogBox default should strip whitespace correctly with newline",
"ReactRefreshLogBox default unterminated JSX",
"ReactRefreshLogBox turbo internal package errors"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"flakey": ["ReactRefreshLogBox turbo conversion to class component (1)"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/development/acceptance/ReactRefreshLogBoxMisc.test.ts": {
"passed": [],
"failed": [],
"pending": [
"ReactRefreshLogBox <Link> component props errors",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox <Link> with multiple children",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"ReactRefreshLogBox server-side only compilation errors"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/development/acceptance/ReactRefreshModule.test.ts": {
"passed": [],
"failed": ["ReactRefreshModule should allow any variable names"],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance/ReactRefreshRegression.test.ts": {
"passed": [
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"ReactRefreshRegression can fast refresh a page with config",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshRegression can fast refresh a page with getServerSideProps",
"ReactRefreshRegression can fast refresh a page with getStaticProps",
"ReactRefreshRegression styled-components hydration mismatch"
],
"failed": [
"ReactRefreshRegression custom loader (mdx) should have Fast Refresh enabled",
"ReactRefreshRegression shows an overlay for a server-side error"
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
"runtimeError": false
},
"test/development/acceptance/ReactRefreshRequire.test.ts": {
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"passed": [
"ReactRefreshRequire bails out if the update bubbles to the root via one of the paths",
"ReactRefreshRequire bails out if update bubbles to the root via the only path",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"ReactRefreshRequire can continue hot updates after module-level errors with ES6 exports",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"ReactRefreshRequire can continue hot updates after module-level errors with module.exports",
"ReactRefreshRequire can replace a module before it is loaded",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"ReactRefreshRequire does not accumulate stale exports over time",
update manifest (#56737) ### What? updates from daily test run Closes WEB-1766
2023-10-13 11:19:54 +02:00
"ReactRefreshRequire propagates a module that stops accepting in next version",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"ReactRefreshRequire provides fresh value for ES6 default import in parents",
"ReactRefreshRequire provides fresh value for ES6 named import in parents",
"ReactRefreshRequire provides fresh value for exports.* in parents",
"ReactRefreshRequire provides fresh value for module.exports in parents",
"ReactRefreshRequire runs dependencies before dependents",
"ReactRefreshRequire stops update propagation after module-level errors"
],
update manifest (#56737) ### What? updates from daily test run Closes WEB-1766
2023-10-13 11:19:54 +02:00
"failed": [],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"pending": [],
"flakey": [
"ReactRefreshRequire propagates a hot update to closest accepted module",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"ReactRefreshRequire propagates hot update to all inverse dependencies",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"ReactRefreshRequire re-runs accepted modules"
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/development/acceptance/component-stack.test.ts": {
"passed": [],
"failed": [
"Component Stack in error overlay should show a component stack on hydration error"
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"test/development/acceptance/error-recovery.test.ts": {
"passed": [
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"ReactRefreshLogBox turbo logbox: can recover from a syntax error without losing state",
"ReactRefreshLogBox turbo stuck error"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
"ReactRefreshLogBox turbo logbox: can recover from a component error",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox turbo logbox: can recover from a event handler error",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"ReactRefreshLogBox turbo render error not shown right after syntax error",
"ReactRefreshLogBox turbo syntax > runtime error"
],
"pending": [
"ReactRefreshLogBox default logbox: can recover from a component error",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ReactRefreshLogBox default logbox: can recover from a event handler error",
"ReactRefreshLogBox default logbox: can recover from a syntax error without losing state",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"ReactRefreshLogBox default render error not shown right after syntax error",
"ReactRefreshLogBox default stuck error",
"ReactRefreshLogBox default syntax > runtime error"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/acceptance/hydration-error.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Error overlay for hydration errors should show correct hydration error when client and server render different text"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/development/acceptance/server-component-compiler-errors-in-pages.test.ts": {
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Error Overlay for server components compiler errors in pages importing 'next/headers' in pages",
"Error Overlay for server components compiler errors in pages importing 'server-only' in pages"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/development/api-cors-with-rewrite/index.test.ts": {
"passed": [
"Rewritten API Requests should pass OPTIONS requests to the api function should pass OPTIONS requests to the api function"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"test/development/app-dir/app-routes-error/index.test.ts": {
"passed": [
"app-dir - app routes errors bad lowercase exports should print an error when using lowercase \"delete\" in dev",
"app-dir - app routes errors bad lowercase exports should print an error when using lowercase \"get\" in dev",
"app-dir - app routes errors bad lowercase exports should print an error when using lowercase \"head\" in dev",
"app-dir - app routes errors bad lowercase exports should print an error when using lowercase \"options\" in dev",
"app-dir - app routes errors bad lowercase exports should print an error when using lowercase \"patch\" in dev",
"app-dir - app routes errors bad lowercase exports should print an error when using lowercase \"post\" in dev",
"app-dir - app routes errors bad lowercase exports should print an error when using lowercase \"put\" in dev"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/development/app-dir/basic/basic.test.ts": {
"passed": ["basic app-dir tests should reload app pages without error"],
"failed": [],
"pending": ["basic app-dir tests should reload app pages without error"],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"test/development/app-dir/experimental-lightningcss/experimental-lightningcss.test.ts": {
"passed": ["experimental-lightningcss should support css modules"],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"test/development/app-dir/multiple-compiles-single-route/multiple-compiles-single-route.test.ts": {
"passed": [
"multiple-compiles-single-route should not compile additional matching paths"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/development/app-dir/strict-mode-enabled-by-default/strict-mode-enabled-by-default.test.ts": {
"passed": ["Strict Mode enabled by default should work using browser"],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/app-hmr/hmr.test.ts": {
"passed": [
"app-dir-hmr filesystem changes should have no unexpected action error for hmr",
"app-dir-hmr filesystem changes should not break when renaming a folder",
"app-dir-hmr filesystem changes should not continously poll when hitting a not found page"
],
"failed": [
"app-dir-hmr filesystem changes should update server components pages when env files is changed (edge)",
"app-dir-hmr filesystem changes should update server components pages when env files is changed (nodejs)"
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": true
},
"test/development/app-render-error-log/app-render-error-log.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-render-error-log should log the correct values on app-render error",
"app-render-error-log should log the correct values on app-render error with edge runtime"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"test/development/basic/asset-prefix/asset-prefix.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": ["asset-prefix should load the app properly without reloading"],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"test/development/basic/barrel-optimization/barrel-optimization.test.ts": {
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"passed": [
"optimizePackageImports should handle recursive wildcard exports",
"optimizePackageImports should not break \"use client\" directive in optimized packages",
"optimizePackageImports should support \"use client\" directive in barrel file"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"optimizePackageImports app - should optimize recursive wildcard export mapping",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"optimizePackageImports app - should render the icons correctly without creating all the modules",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"optimizePackageImports pages - should optimize recursive wildcard export mapping",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"optimizePackageImports pages - should render the icons correctly without creating all the modules",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"optimizePackageImports should support MUI",
"optimizePackageImports should support visx"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"test/development/basic/define-class-fields/define-class-fields.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
"useDefineForClassFields SWC option Initializes resident to undefined after the call to 'super()' when with useDefineForClassFields enabled",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"useDefineForClassFields SWC option set accessors from base classes won’t get triggered with useDefineForClassFields enabled",
"useDefineForClassFields SWC option tsx should compile with useDefineForClassFields enabled"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"test/development/basic/emotion-swc/emotion-swc.test.ts": {
"passed": [],
"failed": ["emotion SWC option should have styling from the css prop"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/basic/gssp-ssr-change-reloading/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"GS(S)P Server-Side Change Reloading should keep scroll position when updating from change in getStaticProps",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"GS(S)P Server-Side Change Reloading should not reload page when client-side is changed too GSP",
"GS(S)P Server-Side Change Reloading should not reload page when client-side is changed too GSSP",
"GS(S)P Server-Side Change Reloading should refresh data when server import is updated",
"GS(S)P Server-Side Change Reloading should show indicator when re-fetching data",
"GS(S)P Server-Side Change Reloading should update on props error in getStaticProps",
"GS(S)P Server-Side Change Reloading should update on thrown error in getStaticProps",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"GS(S)P Server-Side Change Reloading should update page when getServerSideProps is changed only",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"GS(S)P Server-Side Change Reloading should update page when getStaticPaths is changed only",
"GS(S)P Server-Side Change Reloading should update page when getStaticProps is changed only",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"GS(S)P Server-Side Change Reloading should update page when getStaticProps is changed only for /another/index",
"GS(S)P Server-Side Change Reloading should update page when getStaticProps is changed only for /index"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/basic/hmr.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"basic HMR, basePath: \"\" Error Recovery should detect runtime errors on the module scope",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"basic HMR, basePath: \"\" Error Recovery should detect syntax errors and recover",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"basic HMR, basePath: \"\" Error Recovery should not continously poll a custom error page",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"basic HMR, basePath: \"\" Error Recovery should recover after a bad return from the render function",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"basic HMR, basePath: \"\" Error Recovery should recover after an error reported via SSR",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"basic HMR, basePath: \"\" Error Recovery should recover after exporting an invalid page",
"basic HMR, basePath: \"\" Error Recovery should recover after undefined exported as default",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"basic HMR, basePath: \"\" Error Recovery should recover from 404 after a page has been added",
"basic HMR, basePath: \"\" Error Recovery should recover from 404 after a page has been added with dynamic segments",
"basic HMR, basePath: \"\" Hot Module Reloading delete a page and add it back should load the page properly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"basic HMR, basePath: \"\" Hot Module Reloading editing a page should detect the changes and display it",
"basic HMR, basePath: \"\" Hot Module Reloading editing a page should not reload unrelated pages",
"basic HMR, basePath: \"\" Hot Module Reloading editing a page should update styles correctly",
"basic HMR, basePath: \"\" Hot Module Reloading editing a page should update styles in a dynamic component correctly",
"basic HMR, basePath: \"\" Hot Module Reloading editing a page should update styles in a stateful component correctly",
"basic HMR, basePath: \"\" should have correct router.isReady for auto-export page",
"basic HMR, basePath: \"\" should have correct router.isReady for getStaticProps page",
"basic HMR, basePath: \"\" should show hydration error correctly",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"basic HMR, basePath: \"/docs\" Error Recovery should detect runtime errors on the module scope",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"basic HMR, basePath: \"/docs\" Error Recovery should detect syntax errors and recover",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"basic HMR, basePath: \"/docs\" Error Recovery should not continously poll a custom error page",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"basic HMR, basePath: \"/docs\" Error Recovery should recover after a bad return from the render function",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"basic HMR, basePath: \"/docs\" Error Recovery should recover after an error reported via SSR",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"basic HMR, basePath: \"/docs\" Error Recovery should recover after exporting an invalid page",
"basic HMR, basePath: \"/docs\" Error Recovery should recover after undefined exported as default",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"basic HMR, basePath: \"/docs\" Error Recovery should recover from 404 after a page has been added",
"basic HMR, basePath: \"/docs\" Error Recovery should recover from 404 after a page has been added with dynamic segments",
"basic HMR, basePath: \"/docs\" Hot Module Reloading delete a page and add it back should load the page properly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"basic HMR, basePath: \"/docs\" Hot Module Reloading editing a page should detect the changes and display it",
"basic HMR, basePath: \"/docs\" Hot Module Reloading editing a page should not reload unrelated pages",
"basic HMR, basePath: \"/docs\" Hot Module Reloading editing a page should update styles correctly",
"basic HMR, basePath: \"/docs\" Hot Module Reloading editing a page should update styles in a dynamic component correctly",
"basic HMR, basePath: \"/docs\" Hot Module Reloading editing a page should update styles in a stateful component correctly",
"basic HMR, basePath: \"/docs\" should have correct router.isReady for auto-export page",
"basic HMR, basePath: \"/docs\" should have correct router.isReady for getStaticProps page",
"basic HMR, basePath: \"/docs\" should show hydration error correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"basic HMR, basePath: \"\" Error Recovery should recover after loader parse error in an imported file",
"basic HMR, basePath: \"\" Error Recovery should recover after webpack parse error in an imported file",
"basic HMR, basePath: \"\" Error Recovery should recover from errors in getInitialProps in client",
"basic HMR, basePath: \"\" Error Recovery should recover from errors in the render function",
"basic HMR, basePath: \"\" Full reload should warn about full reload in cli output - anonymous page function",
"basic HMR, basePath: \"\" Full reload should warn about full reload in cli output - runtime-error",
"basic HMR, basePath: \"\" should have correct compile timing after fixing error",
"basic HMR, basePath: \"/docs\" Error Recovery should recover after loader parse error in an imported file",
"basic HMR, basePath: \"/docs\" Error Recovery should recover after webpack parse error in an imported file",
"basic HMR, basePath: \"/docs\" Error Recovery should recover from errors in getInitialProps in client",
"basic HMR, basePath: \"/docs\" Error Recovery should recover from errors in the render function",
"basic HMR, basePath: \"/docs\" Full reload should warn about full reload in cli output - anonymous page function",
"basic HMR, basePath: \"/docs\" Full reload should warn about full reload in cli output - runtime-error",
"basic HMR, basePath: \"/docs\" should have correct compile timing after fixing error"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/development/basic/legacy-decorators.test.ts": {
"passed": [
"Legacy decorators SWC option should compile with legacy decorators enabled"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/development/basic/misc.test.ts": {
"passed": [
"misc basic dev tests, basePath: \"\" Development Logs should not warn when prefetch is false",
"misc basic dev tests, basePath: \"\" Development Logs should not warn when prefetch is not specified",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"misc basic dev tests, basePath: \"\" Development Logs should warn when prefetch is true",
"misc basic dev tests, basePath: \"\" With Security Related Issues should handle encoded / value for trailing slash correctly",
"misc basic dev tests, basePath: \"\" With Security Related Issues should not allow accessing files outside .next/static and .next/server directory",
"misc basic dev tests, basePath: \"\" should allow access to public files",
"misc basic dev tests, basePath: \"\" should set process.env.NODE_ENV in development",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"misc basic dev tests, basePath: \"/docs\" Development Logs should not warn when prefetch is false",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"misc basic dev tests, basePath: \"/docs\" Development Logs should not warn when prefetch is not specified",
"misc basic dev tests, basePath: \"/docs\" Development Logs should warn when prefetch is true",
"misc basic dev tests, basePath: \"/docs\" With Security Related Issues should handle encoded / value for trailing slash correctly",
"misc basic dev tests, basePath: \"/docs\" With Security Related Issues should not allow accessing files outside .next/static and .next/server directory",
"misc basic dev tests, basePath: \"/docs\" should allow access to public files",
"misc basic dev tests, basePath: \"/docs\" should set process.env.NODE_ENV in development"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/basic/next-dynamic.test.ts": {
"passed": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import custom loading should render custom loading on the server side when `ssr:false` and `loading` is provided",
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import custom loading should render the component on client side",
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import default behavior should SSR nested dynamic components and skip nonSSR ones",
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import default behavior should hydrate nested chunks",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import default behavior should render dynamic import components",
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import default behavior should render dynamic import components using a function as first parameter",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import default behavior should render even there are no physical chunk exists",
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import default behavior should render the component Head content",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import ssr:false option should import and render the ESM module correctly on client side",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import ssr:false option should not render loading on the server side",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import ssr:false option should render the component on client side",
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import ssr:true option Should render the component on the server side",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import ssr:true option should render the component on client side",
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import custom loading should render custom loading on the server side when `ssr:false` and `loading` is provided",
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import custom loading should render the component on client side",
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import default behavior should SSR nested dynamic components and skip nonSSR ones",
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import default behavior should hydrate nested chunks",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import default behavior should render dynamic import components",
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import default behavior should render dynamic import components using a function as first parameter",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import default behavior should render even there are no physical chunk exists",
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import default behavior should render the component Head content",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import ssr:false option should import and render the ESM module correctly on client side",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import ssr:false option should not render loading on the server side",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import ssr:false option should render the component on client side",
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import ssr:true option Should render the component on the server side",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import ssr:true option should render the component on client side",
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import custom loading should render custom loading on the server side when `ssr:false` and `loading` is provided",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import custom loading should render the component on client side",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import default behavior should SSR nested dynamic components and skip nonSSR ones",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import default behavior should hydrate nested chunks",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import default behavior should render dynamic import components",
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import default behavior should render dynamic import components using a function as first parameter",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import default behavior should render even there are no physical chunk exists",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import default behavior should render the component Head content",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import ssr:false option should import and render the ESM module correctly on client side",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import ssr:false option should not render loading on the server side",
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import ssr:false option should render the component on client side",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import ssr:true option Should render the component on the server side",
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import ssr:true option should render the component on client side"
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
],
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import Multiple modules should only include the rendered module script tag",
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import Multiple modules should only load the rendered module in the browser",
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import Multiple modules should only render one bundle if component is used multiple times",
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import custom chunkfilename should render the component on client side",
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import custom chunkfilename should render the correct filename",
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import custom loading should render custom loading on the server side when `ssr:false` and `loading` is provided",
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import custom loading should render the component on client side",
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import default behavior should SSR nested dynamic components and skip nonSSR ones",
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import default behavior should hydrate nested chunks",
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import default behavior should render dynamic import components",
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import default behavior should render dynamic import components using a function as first parameter",
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import default behavior should render even there are no physical chunk exists",
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import default behavior should render the component Head content",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import ssr:false option should import and render the ESM module correctly on client side",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import ssr:false option should not render loading on the server side",
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import ssr:false option should render the component on client side",
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import ssr:true option Should render the component on the server side",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"basic next/dynamic usage, basePath: \"\" with \"babel\" compiler babel Dynamic import ssr:true option should render the component on client side",
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import Multiple modules should only include the rendered module script tag",
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import Multiple modules should only load the rendered module in the browser",
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import Multiple modules should only render one bundle if component is used multiple times",
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import custom chunkfilename should render the component on client side",
"basic next/dynamic usage, basePath: \"\" with \"document.getInitialProps\" compiler document.getInitialProps Dynamic import custom chunkfilename should render the correct filename",
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import Multiple modules should only include the rendered module script tag",
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import Multiple modules should only load the rendered module in the browser",
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import Multiple modules should only render one bundle if component is used multiple times",
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import custom chunkfilename should render the component on client side",
"basic next/dynamic usage, basePath: \"\" with \"swc\" compiler swc Dynamic import custom chunkfilename should render the correct filename",
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import Multiple modules should only include the rendered module script tag",
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import Multiple modules should only load the rendered module in the browser",
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import Multiple modules should only render one bundle if component is used multiple times",
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import custom chunkfilename should render the component on client side",
"basic next/dynamic usage, basePath: \"/docs\" with \"swc\" compiler swc Dynamic import custom chunkfilename should render the correct filename"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"runtimeError": false
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"test/development/basic/next-rs-api.test.ts": {
"passed": [
"next.rs api should allow to write app Node.js page to disk",
"next.rs api should allow to write app Node.js route to disk",
update manifest (#56737) ### What? updates from daily test run Closes WEB-1766
2023-10-13 11:19:54 +02:00
"next.rs api should allow to write app edge page to disk",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next.rs api should allow to write app edge route to disk",
"next.rs api should allow to write pages Node.js api to disk",
"next.rs api should allow to write pages Node.js page to disk",
"next.rs api should allow to write pages edge api to disk",
"next.rs api should allow to write pages edge page to disk",
"next.rs api should allow to write root page to disk",
"next.rs api should detect the correct routes",
"next.rs api should have working HMR on client and server-side change on a page 0",
"next.rs api should have working HMR on client and server-side change on a page 1",
"next.rs api should have working HMR on client and server-side change on a page 2",
"next.rs api should have working HMR on client-side change on a app page 0",
"next.rs api should have working HMR on client-side change on a app page 1",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"next.rs api should have working HMR on client-side change on a app page 2",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next.rs api should have working HMR on client-side change on a page 0",
"next.rs api should have working HMR on client-side change on a page 1",
"next.rs api should have working HMR on client-side change on a page 2",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"next.rs api should have working HMR on server-side change on a app page 0",
"next.rs api should have working HMR on server-side change on a app page 1",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next.rs api should have working HMR on server-side change on a app page 2",
"next.rs api should have working HMR on server-side change on a page 0",
"next.rs api should have working HMR on server-side change on a page 1",
"next.rs api should have working HMR on server-side change on a page 2"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"pending": ["next.rs api should allow to make many HMR updates"],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/development/basic/node-builtins.test.ts": {
"passed": [
"node builtins should have polyfilled node.js builtins for the browser correctly",
"node builtins should have polyfilled node.js builtins for the browser correctly in client component",
"node builtins should support node.js builtins",
"node builtins should support node.js builtins in server component",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"node builtins should support node.js builtins prefixed by node:",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"node builtins should support node.js builtins prefixed by node: in server component"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/development/basic/project-directory-rename.test.ts": {
"passed": [],
"failed": [],
"pending": [
"Project Directory Renaming should detect project dir rename and restart"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/development/basic/styled-components-disabled.test.ts": {
"passed": [],
"failed": [
"styled-components SWC transform should have hydration mismatch with styled-components transform disabled"
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/basic/styled-components.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"styled-components SWC transform should contain styles in initial HTML",
"styled-components SWC transform should not have hydration mismatch with styled-components transform enabled",
"styled-components SWC transform should only render once on the server per request",
"styled-components SWC transform should render the page with correct styles"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"styled-components SWC transform should enable the display name transform by default"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/basic/tailwind-jit.test.ts": {
"passed": ["TailwindCSS JIT works with JIT enabled"],
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"test/development/basic/theme-ui/theme-ui.test.ts": {
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"passed": ["theme-ui SWC option should have theme provided styling"],
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/client-dev-overlay/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"client-dev-overlay should be able to fullscreen the minimized overlay",
"client-dev-overlay should be able to hide the minimized overlay",
"client-dev-overlay should be able to minimize the fullscreen overlay",
"client-dev-overlay should have a role of \"dialog\" if the page is focused"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/correct-tsconfig-defaults/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"correct tsconfig.json defaults should add `moduleResolution` when generating tsconfig.json in dev",
"correct tsconfig.json defaults should not warn for `moduleResolution` when already present and valid"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/dotenv-default-expansion/index.test.ts": {
"passed": ["Dotenv default expansion should work"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"test/development/duplicate-pages/duplicate-pages.test.ts": {
"passed": ["Handles Duplicate Pages Shows warning in development"],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/experimental-https-server/https-server.generated-key.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"experimental-https-server (generated certificate) only runs on CI as it requires administrator privileges"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/experimental-https-server/https-server.provided-key.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"experimental-https-server (provided certificate) should successfully load the app in app dir",
"experimental-https-server (provided certificate) should successfully load the app in pages dir"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/gssp-notfound/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"getServerSideProps returns notFound: true should not poll indefinitely"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/jsconfig-path-reloading/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"jsconfig-path-reloading jsconfig added after starting dev should load with initial paths config correctly",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"jsconfig-path-reloading jsconfig should load with initial paths config correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"flakey": [
"jsconfig-path-reloading jsconfig added after starting dev should automatically fast refresh content when path is added without error",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"jsconfig-path-reloading jsconfig added after starting dev should recover from module not found when paths is updated",
"jsconfig-path-reloading jsconfig should automatically fast refresh content when path is added without error",
"jsconfig-path-reloading jsconfig should recover from module not found when paths is updated"
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/middleware-errors/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"middleware - development errors when middleware contains an unhandled rejection does not render the error",
"middleware - development errors when middleware contains an unhandled rejection logs the error correctly",
"middleware - development errors when middleware throws synchronously renders the error correctly and recovers",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"middleware - development errors when running invalid dynamic code with eval logs the error correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"middleware - development errors when there is a compilation error after boot renders the error correctly and recovers",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"middleware - development errors when there is a compilation error from boot renders the error correctly and recovers",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"middleware - development errors when there is an unhandled rejection while loading a dependency does not render the error",
"middleware - development errors when there is an unhandled rejection while loading a dependency logs the error correctly",
"middleware - development errors when there is an unhandled rejection while loading the module does not render the error",
"middleware - development errors when there is an unhandled rejection while loading the module logs the error correctly"
],
"failed": [
"middleware - development errors when middleware throws synchronously logs the error correctly",
"middleware - development errors when running invalid dynamic code with eval renders the error correctly and recovers",
"middleware - development errors when throwing while loading the module logs the error correctly",
"middleware - development errors when throwing while loading the module renders the error correctly and recovers"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"flakey": [
"middleware - development errors when there is a compilation error after boot logs the error correctly",
"middleware - development errors when there is a compilation error from boot logs the error correctly"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/middleware-warnings/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"middlewares does not warn when populating response with a function call",
"middlewares does not warn when populating response with a value",
"middlewares does not warn when populating response with an async function call",
"middlewares does not warn when returning null reponse body",
"middlewares does not warn when returning response with JSON.stringify",
"middlewares does not warn when returning response with literal number",
"middlewares does not warn when returning response with literal string",
"middlewares does not warn when returning undefined response body"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/next-font/build-errors.test.ts": {
"passed": [],
"failed": [
"build-errors should show a module not found error if local font file can' be resolved",
"build-errors should show a next/font error when input is wrong"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/next-font/deprecated-package.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Deprecated @next/font warning should not warn if @next/font is not in deps",
"Deprecated @next/font warning should warn if @next/font is in deps"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/next-font/font-loader-in-document-error.test.ts": {
"passed": [],
"failed": ["font-loader-in-document-error next/font inside _document"],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/development/pages-dir/client-navigation/index.test.ts": {
"passed": [
"Client Navigation Rendering via HTTP 404 should 404 on not existent page",
"Client Navigation Rendering via HTTP 404 should 404 on wrong casing",
"Client Navigation Rendering via HTTP 404 should not 404 for <page>/",
"Client Navigation Rendering via HTTP 404 should should not contain a page script in a 404 page",
"Client Navigation Rendering via HTTP allows to import .json files",
"Client Navigation Rendering via HTTP asPath",
"Client Navigation Rendering via HTTP default Content-Type",
"Client Navigation Rendering via HTTP default export is not a React Component",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"Client Navigation Rendering via HTTP error-in-the-global-scope",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Client Navigation Rendering via HTTP error-inside-page",
"Client Navigation Rendering via HTTP getInitialProps circular structure",
"Client Navigation Rendering via HTTP getInitialProps resolves to null",
"Client Navigation Rendering via HTTP getInitialProps should be class method",
"Client Navigation Rendering via HTTP header helper avoids dedupe of meta tags with the same name if they use unique keys",
"Client Navigation Rendering via HTTP header helper avoids dedupe of specific tags",
"Client Navigation Rendering via HTTP header helper dedupes tags",
"Client Navigation Rendering via HTTP header helper dedupes tags with the same key as the default",
"Client Navigation Rendering via HTTP header helper renders Fragment children",
"Client Navigation Rendering via HTTP header helper renders boolean attributes correctly children",
"Client Navigation Rendering via HTTP header helper renders header information",
"Client Navigation Rendering via HTTP header renders default charset",
"Client Navigation Rendering via HTTP header renders default viewport",
"Client Navigation Rendering via HTTP renders a link component",
"Client Navigation Rendering via HTTP renders a stateless component",
"Client Navigation Rendering via HTTP renders properties populated asynchronously",
"Client Navigation Rendering via HTTP renders styled jsx",
"Client Navigation Rendering via HTTP renders styled jsx external",
"Client Navigation Rendering via HTTP renders when component is a forwardRef instance",
"Client Navigation Rendering via HTTP renders when component is a memo instance",
"Client Navigation Rendering via HTTP renders with fragment syntax",
"Client Navigation Rendering via HTTP setting Content-Type in getInitialProps",
"Client Navigation Rendering via HTTP should handle undefined prop in head server-side",
"Client Navigation Rendering via HTTP should place charset element at the top of <head>",
"Client Navigation Rendering via HTTP should render 404 for _next routes that do not exist",
"Client Navigation Rendering via HTTP should render page that has module.exports anywhere",
"Client Navigation Rendering via HTTP should render the page with `nextExport` property",
"Client Navigation Rendering via HTTP should render the page with custom extension",
"Client Navigation Rendering via HTTP should render the page without `err` property",
"Client Navigation Rendering via HTTP should render the page without `nextExport` property",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"Client Navigation Rendering via HTTP should set Cache-Control header",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Client Navigation Rendering via HTTP should should not contain scripts that are not js",
"Client Navigation Rendering via HTTP should show a valid error when undefined is thrown",
"Client Navigation Rendering via HTTP with the HOC based router should include asPath",
"Client Navigation Rendering via HTTP with the HOC based router should navigate as expected",
"Client Navigation foreign history manipulation should ignore foreign history state with missing properties",
"Client Navigation foreign history manipulation should ignore history state with an invalid url",
"Client Navigation foreign history manipulation should ignore history state without options",
"Client Navigation resets scroll at the correct time should intentionally not reset scroll before the new page runs its lifecycles (Router#push)",
"Client Navigation resets scroll at the correct time should reset scroll before the new page runs its lifecycles (<Link />)",
"Client Navigation resets scroll at the correct time should reset scroll before the new page runs its lifecycles (Router#push)",
"Client Navigation should emit routeChangeError on hash change cancel",
"Client Navigation should handle undefined prop in head client-side",
"Client Navigation should navigate to paths relative to the current page",
"Client Navigation should not error on module.exports + polyfills",
"Client Navigation should not reload when visiting /_error directly",
"Client Navigation should scroll to top when the scroll option is set to true",
"Client Navigation should work on nested /index/index.js",
"Client Navigation updating head while client routing should not warn when application/ld+json scripts are in head",
"Client Navigation updating head while client routing should only execute async and defer scripts once",
"Client Navigation updating head while client routing should update head during client routing",
"Client Navigation updating head while client routing should update head when unmounting component",
"Client Navigation updating head while client routing should update title during client routing",
"Client Navigation updating head while client routing should warn when scripts are in head",
"Client Navigation updating head while client routing should warn when stylesheets or scripts are in head",
"Client Navigation with 404 pages should 404 on not existent page",
"Client Navigation with 404 pages should 404 on wrong casing",
"Client Navigation with 404 pages should 404 on wrong casing of url dynamic param",
"Client Navigation with 404 pages should get url dynamic param",
"Client Navigation with 404 pages should not 404 for <page>/",
"Client Navigation with 404 pages should should not contain a page script in a 404 page",
"Client Navigation with <Link/> should call mouse handlers with an absolute url",
"Client Navigation with <Link/> should error when calling onClick without event",
"Client Navigation with <Link/> should have proper error when no children are provided",
"Client Navigation with <Link/> should navigate an absolute local url",
"Client Navigation with <Link/> should navigate an absolute local url with as",
"Client Navigation with <Link/> should navigate an absolute url",
"Client Navigation with <Link/> should navigate back after reload",
"Client Navigation with <Link/> should navigate forwards after reload",
"Client Navigation with <Link/> should navigate the page",
"Client Navigation with <Link/> should navigate via the client side",
"Client Navigation with <Link/> should not throw error when one number type child is provided",
"Client Navigation with <a/> tag inside the <Link /> should navigate the page",
"Client Navigation with <a/> tag inside the <Link /> should not navigate if the <a/> tag has a target",
"Client Navigation with <a/> tag inside the <Link /> should not navigate if the click-event is modified",
"Client Navigation with <a/> tag inside the <Link /> should not reload when link in svg is clicked",
"Client Navigation with URL objects should handle undefined in router.push",
"Client Navigation with URL objects should work with \"Router.push\"",
"Client Navigation with URL objects should work with <Link/>",
"Client Navigation with URL objects should work with the \"replace\" prop",
"Client Navigation with asPath inside getInitialProps should show the correct asPath with a Link with as prop",
"Client Navigation with asPath inside getInitialProps should show the correct asPath with a Link without the as prop",
"Client Navigation with asPath with next/link should detect asPath query changes correctly",
"Client Navigation with asPath with next/link should use pushState with same href and different asPath",
"Client Navigation with asPath with next/router should navigate an absolute local url on push",
"Client Navigation with asPath with next/router should navigate an absolute local url on replace",
"Client Navigation with asPath with next/router should navigate an absolute url on push",
"Client Navigation with asPath with next/router should navigate an absolute url on replace",
"Client Navigation with asPath with next/router should show the correct asPath",
"Client Navigation with different types of urls should not work with /index page",
"Client Navigation with different types of urls should work with / page",
"Client Navigation with different types of urls should work with dir/ page",
"Client Navigation with different types of urls should work with normal page",
"Client Navigation with empty getInitialProps() should render an error",
"Client Navigation with getInitialProp redirect should redirect the page via client side",
"Client Navigation with getInitialProp redirect should redirect the page when loading",
"Client Navigation with hash changes check hydration mis-match should not have hydration mis-match for hash link",
"Client Navigation with hash changes when hash change via A tag should not run getInitialProps",
"Client Navigation with hash changes when hash change via Link Should update asPath",
"Client Navigation with hash changes when hash change via Link should not run getInitialProps",
"Client Navigation with hash changes when hash change via Link should not scroll to hash when scroll={false} is set",
"Client Navigation with hash changes when hash change via Link should scroll to the specified CJK position to a new page",
"Client Navigation with hash changes when hash change via Link should scroll to the specified position on the same page",
"Client Navigation with hash changes when hash change via Link should scroll to the specified position on the same page with a name property",
"Client Navigation with hash changes when hash change via Link should scroll to the specified position to a new page",
"Client Navigation with hash changes when hash get removed should not run getInitialProps",
"Client Navigation with hash changes when hash get removed should not run getInitialProps when removing via back",
"Client Navigation with hash changes when hash set to empty should not run getInitialProps",
"Client Navigation with hash changes with state when passing state via hash change should increment the history state counter",
"Client Navigation with hash changes with state when passing state via hash change should increment the shallow history state counter",
"Client Navigation with onClick action should always replace the state and perform additional action",
"Client Navigation with onClick action should not reload if default was prevented",
"Client Navigation with onClick action should reload the page and perform additional action",
"Client Navigation with querystring relative urls should work with Link",
"Client Navigation with querystring relative urls should work with router.push",
"Client Navigation with querystring relative urls should work with router.replace",
"Client Navigation with shallow routing should handle the back button and should not run getInitialProps",
"Client Navigation with shallow routing should keep the scroll position on shallow routing",
"Client Navigation with shallow routing should run getInitialProps always when rending the page to the screen",
"Client Navigation with shallow routing should update the url without running getInitialProps",
"Client Navigation with the HOC based router should navigate as expected",
"Client Navigation with the current url should always replace the state",
"Client Navigation with the current url should reload the page",
"Client Navigation with the same page but different querystring should navigate the page",
"Client Navigation with the same page but different querystring should remove querystring",
"Client Navigation with unexpected <a/> nested tag should not redirect if passHref prop is not defined in Link",
"Client Navigation with unexpected <a/> nested tag should redirect if passHref prop is defined in Link"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [
"Client Navigation runtime errors should show redbox when a client side error is thrown inside a component",
"Client Navigation runtime errors should show redbox when a client side error is thrown outside a component"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/pages-dir/custom-app-hmr/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [
"custom-app-hmr should not do full reload when simply editing _app.js"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/project-directory-with-styled-jsx-suffix/index.test.ts": {
"passed": ["project directory with styled-jsx suffix should work"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/repeated-dev-edits/repeated-dev-edits.test.ts": {
"passed": ["repeated-dev-edits should not break the hydration "],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/tsconfig-path-reloading/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Turbopack: Align some "Module not found" errors with webpack (#58518) This: - Sends an hmr sync event so that errors that occur after the initial hmr connection are sent to the client - Aligns on `path/to/file.js:line:column` format across error overlay implementations in the cli and on the web - Adapts "Module not found" errors from Turbopack to include Next.js-relevant formatting and documentation links to align with webpack Test Plan: Passes 3 tests that were previously failing Closes PACK-1974 --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by: Leah <github.leah@hrmny.sh> Co-authored-by: Zack Tanner <zacktanner@gmail.com>
2023-11-30 17:34:56 +01:00
"tsconfig-path-reloading tsconfig should load with initial paths config correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [
"tsconfig-path-reloading tsconfig added after starting dev should recover from module not found when paths is updated",
"tsconfig-path-reloading tsconfig should recover from module not found when paths is updated"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"flakey": [
"tsconfig-path-reloading tsconfig added after starting dev should automatically fast refresh content when path is added without error",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"tsconfig-path-reloading tsconfig added after starting dev should load with initial paths config correctly",
"tsconfig-path-reloading tsconfig should automatically fast refresh content when path is added without error"
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/typescript-auto-install/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"typescript-auto-install should detect TypeScript being added and auto setup",
"typescript-auto-install should work"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/watch-config-file/index.test.ts": {
"passed": ["watch-config-file should output config file change"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/development/webpack-issuer-deprecation-warning/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"webpack-issuer-deprecation-warning should not appear deprecation warning about webpack module issuer"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/404-page-router/index.test.ts": {
fix(turbopack): `e2e/404-page-router` test (#58146)
2023-11-22 19:30:26 +01:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"404-page-router 404-page-router with basePath of false and i18n of false and middleware false for /not/a/real/page should have the correct router parameters after it is ready",
"404-page-router 404-page-router with basePath of false and i18n of false and middleware false for /not/a/real/page?with=query should have the correct router parameters after it is ready",
"404-page-router 404-page-router with basePath of false and i18n of false and middleware false should not throw any errors when re-fetching the route info",
"404-page-router 404-page-router with basePath of false and i18n of true and middleware false for /not/a/real/page should have the correct router parameters after it is ready",
"404-page-router 404-page-router with basePath of false and i18n of true and middleware false for /not/a/real/page?with=query should have the correct router parameters after it is ready",
"404-page-router 404-page-router with basePath of false and i18n of true and middleware false should not throw any errors when re-fetching the route info",
"404-page-router 404-page-router with basePath of true and i18n of false and middleware false for /not/a/real/page should have the correct router parameters after it is ready",
"404-page-router 404-page-router with basePath of true and i18n of false and middleware false for /not/a/real/page?with=query should have the correct router parameters after it is ready",
"404-page-router 404-page-router with basePath of true and i18n of false and middleware false should not throw any errors when re-fetching the route info",
"404-page-router 404-page-router with basePath of true and i18n of true and middleware false for /not/a/real/page should have the correct router parameters after it is ready",
"404-page-router 404-page-router with basePath of true and i18n of true and middleware false for /not/a/real/page?with=query should have the correct router parameters after it is ready",
"404-page-router 404-page-router with basePath of true and i18n of true and middleware false should not throw any errors when re-fetching the route info"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
fix(turbopack): `e2e/404-page-router` test (#58146)
2023-11-22 19:30:26 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir-legacy-edge-runtime-config/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir edge runtime config should warn the legacy object config export"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/_allow-underscored-root-directory/_allow-underscored-root-directory.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"_allow-underscored-root-directory should not serve app path with underscore",
"_allow-underscored-root-directory should pages path with a underscore at the root"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"_allow-underscored-root-directory should serve app path with %5F"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"test/e2e/app-dir/actions-allowed-origins/app-action-allowed-origins.test.ts": {
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"passed": [
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"app-dir action allowed origins should pass if localhost is set as a safe origin"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"test/e2e/app-dir/actions-allowed-origins/app-action-disallowed-origins.test.ts": {
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"passed": [
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"app-dir action disallowed origins should error if x-forwarded-host does not match the origin"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/e2e/app-dir/actions-navigation/index.test.ts": {
"passed": [
"app-dir action handling should handle actions correctly after following a relative link",
"app-dir action handling should handle actions correctly after navigation / redirection events"
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/actions/app-action-export.test.ts": {
"passed": ["app-dir action handling - next export skip test for dev mode"],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"test/e2e/app-dir/actions/app-action-form-state.test.ts": {
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"passed": [
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"app-dir action useFormState should send the action to the provided permalink with form state when JS disabled",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"app-dir action useFormState should support hydrating the app from progressively enhanced form request",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"app-dir action useFormState should support submitting form state with JS",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"app-dir action useFormState should support submitting form state without JS"
],
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [],
"flakey": [],
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"runtimeError": false
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/actions/app-action-progressive-enhancement.test.ts": {
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir action progressive enhancement should support actions from client without JS",
"app-dir action progressive enhancement should support formData and redirect without JS"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/actions/app-action-size-limit-invalid.test.ts": {
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir action size limit invalid config skip test for dev mode"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/actions/app-action.test.ts": {
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"passed": [
turbopack: Fix Server Actions in Edge runtime (#57462) ### What? Changes Server Actions to use a lazy `require()` statement instead of a lazy dynamic `import()`, to fix SA in the Edge runtime. ### Why? The Edge runtime has a restriction that it's not allowed to lazy load more files. The problem is that dynamic `import()` does exactly that, it defers importing those files until the call time. `require()` doesn't have this issue, because the chunks it would load are included instead of deferred. ### How? Just needed to modify the actions loader entry point… after hours of trying to get the action loader to evaluate in the node runtime and then import the actions in the edge runtime. Closes WEB-1874
2023-10-26 05:51:11 +02:00
"app-dir action handling Edge SSR should allow cookie and header async storages",
"app-dir action handling Edge SSR should handle basic actions correctly",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"app-dir action handling Edge SSR should handle redirect to a relative URL in a single pass",
turbopack: Fix Server Actions in Edge runtime (#57462) ### What? Changes Server Actions to use a lazy `require()` statement instead of a lazy dynamic `import()`, to fix SA in the Edge runtime. ### Why? The Edge runtime has a restriction that it's not allowed to lazy load more files. The problem is that dynamic `import()` does exactly that, it defers importing those files until the call time. `require()` doesn't have this issue, because the chunks it would load are included instead of deferred. ### How? Just needed to modify the actions loader entry point… after hours of trying to get the action loader to evaluate in the node runtime and then import the actions in the edge runtime. Closes WEB-1874
2023-10-26 05:51:11 +02:00
"app-dir action handling Edge SSR should handle regular redirects",
"app-dir action handling Edge SSR should handle unicode search params",
"app-dir action handling Edge SSR should return error response for hoc auth wrappers in edge runtime",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"app-dir action handling HMR should support updating the action",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"app-dir action handling caching disabled by default should not override force-cache in server action",
"app-dir action handling caching disabled by default should not override revalidate in server action",
"app-dir action handling caching disabled by default should use no-store as default for server action",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app-dir action handling encryption should send encrypted values from the closed over closure",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app-dir action handling fetch actions should handle a fetch action initiated from a static page",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"app-dir action handling fetch actions should handle redirect to a relative URL in a single pass",
"app-dir action handling fetch actions should handle regular redirects",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app-dir action handling fetch actions should handle revalidatePath",
"app-dir action handling fetch actions should handle revalidateTag",
"app-dir action handling fetch actions should invalidate client cache on other routes when cookies.set is called",
"app-dir action handling fetch actions should invalidate client cache when path is revalidated",
"app-dir action handling fetch actions should invalidate client cache when tag is revalidated",
"app-dir action handling fetch actions should revalidate when cookies.set is called",
"app-dir action handling fetch actions should revalidate when cookies.set is called in a client action",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir action handling fetch actions should store revalidation data in the prefetch cache",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"app-dir action handling redirects redirects properly when server action handler redirects with a 307 status code",
"app-dir action handling redirects redirects properly when server action handler redirects with a 308 status code",
"app-dir action handling redirects redirects properly when server action handler uses `permanentRedirect`",
"app-dir action handling redirects redirects properly when server action handler uses `redirect`",
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"app-dir action handling server actions render client components server component imported action should support importing client components from actions",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"app-dir action handling should 404 when POSTing an invalid server action",
turbopack: Support Actions in both RSC and Client layers (#57475) ### What? Adds support for Server Actions imported by both server and client. ### Why? If an Action is imported by both the Client and RSC layers, we need to support them as if they're the same action. ### How? First, we need to ensure both layers create the same action hash ids, which we can then use to deduplicate actions imported by both layers. If a conflict is found, we prefer the RSC layer's action. Closes WEB-1879 --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-10-26 08:32:04 +02:00
"app-dir action handling should bundle external libraries if they are on the action layer",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"app-dir action handling should handle actions executed in quick succession",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir action handling should handle basic actions correctly",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"app-dir action handling should log a warning when a server action is not found but an id is provided",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir action handling should not block navigation events while a server action is in flight",
"app-dir action handling should only submit action once when resubmitting an action after navigation",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"app-dir action handling should push new route when redirecting",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir action handling should support .bind",
"app-dir action handling should support chained .bind",
"app-dir action handling should support formData and redirect",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"app-dir action handling should support headers and cookies",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir action handling should support headers in client imported actions",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"app-dir action handling should support hoc auth wrappers",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir action handling should support importing actions in client components",
turbopack: Support Actions in both RSC and Client layers (#57475) ### What? Adds support for Server Actions imported by both server and client. ### Why? If an Action is imported by both the Client and RSC layers, we need to support them as if they're the same action. ### How? First, we need to ensure both layers create the same action hash ids, which we can then use to deduplicate actions imported by both layers. If a conflict is found, we prefer the RSC layer's action. Closes WEB-1879 --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-10-26 08:32:04 +02:00
"app-dir action handling should support importing the same action module instance in both server and action layers",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir action handling should support next/dynamic with ssr: false",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"app-dir action handling should support next/dynamic with ssr: false (edge)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir action handling should support notFound",
"app-dir action handling should support notFound (javascript disabled)",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"app-dir action handling should support setting cookies in route handlers with the correct overrides",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"app-dir action handling should support uploading files",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"app-dir action handling should trigger a refresh for a server action that gets discarded due to a navigation",
"app-dir action handling should work with interception routes"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: Support Actions in both RSC and Client layers (#57475) ### What? Adds support for Server Actions imported by both server and client. ### Why? If an Action is imported by both the Client and RSC layers, we need to support them as if they're the same action. ### How? First, we need to ensure both layers create the same action hash ids, which we can then use to deduplicate actions imported by both layers. If a conflict is found, we prefer the RSC layer's action. Closes WEB-1879 --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-10-26 08:32:04 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"app-dir action handling fetch actions should handle revalidateTag + redirect",
"app-dir action handling server actions render client components client component imported action should support importing client components from actions"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-a11y/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app a11y features route announcer should announce document.title changes",
"app a11y features route announcer should announce h1 changes",
"app a11y features route announcer should announce route changes when h1 changes inside an inner layout",
"app a11y features route announcer should not announce the initital title"
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-alias/app-alias.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir alias should handle typescript paths alias correctly",
"app-dir alias should resolve css imports from outside with src folder presented"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-basepath/index.test.ts": {
"passed": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app dir - basepath should prefix redirect() with basePath",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"app dir - basepath should render usePathname without the basePath",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"app dir - basepath should support Link with basePath prefixed",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - basepath should support `basePath`"
],
"failed": [
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"app dir - basepath should prefix metadata og image with basePath"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-client-cache/client-cache.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": ["app dir client cache semantics should skip dev"],
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-compilation/index.test.ts": {
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"flakey": ["app dir HMR should not cause error when removing loading.js"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"test/e2e/app-dir/app-config-crossorigin/index.test.ts": {
enable e2e tests with turbopack (#57432) Closes WEB-1862 --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-10-25 19:46:31 +02:00
"passed": [],
"failed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"app dir - crossOrigin config should render correctly with assetPrefix: \"/\""
],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-css-pageextensions/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - css with pageextensions css support with pageextensions page in app directory with pageextention, css should work should support global css inside layout"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-css/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - css HMR should not break HMR when CSS is imported in a server component",
"app dir - css HMR should support HMR for CSS imports in client components",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - css HMR should support HMR for CSS imports in server components",
"app dir - css HMR should support HMR with sass/scss",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - css css support client components should support css modules inside client components",
"app dir - css css support client components should support css modules inside client page",
"app dir - css css support client layouts should support css modules inside client layouts",
"app dir - css css support client layouts should support global css inside client layouts",
"app dir - css css support client pages should support css modules inside client pages",
"app dir - css css support client pages should support global css inside client pages",
"app dir - css css support css ordering should have inner layers take precedence over outer layers",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"app dir - css css support multiple entries should deduplicate styles on the module level",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - css css support page extensions should include css imported in MDX pages",
"app dir - css css support server layouts should support css modules inside server layouts",
"app dir - css css support server pages should not contain pages css in app dir page",
"app dir - css css support server pages should support css modules inside server pages",
"app dir - css css support server pages should support global css inside server pages",
"app dir - css css support should not affect css orders during HMR",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - css css support should reload @import styles during HMR",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - css css support special entries should include css imported in client not-found.js",
"app dir - css css support special entries should include css imported in client template.js",
"app dir - css css support special entries should include css imported in error.js",
"app dir - css css support special entries should include css imported in root not-found.js",
"app dir - css css support special entries should include css imported in server not-found.js",
"app dir - css css support special entries should include css imported in server template.js",
"app dir - css css support special entries should include root layout css for root not-found.js",
"app dir - css sass support client layouts should support global sass/scss inside client layouts",
"app dir - css sass support client layouts should support sass/scss modules inside client layouts",
"app dir - css sass support client pages should support global sass/scss inside client pages",
"app dir - css sass support client pages should support sass/scss modules inside client pages",
"app dir - css sass support server layouts should support global sass/scss inside server layouts",
"app dir - css sass support server layouts should support sass/scss modules inside server layouts",
"app dir - css sass support server pages should support global sass/scss inside server pages",
"app dir - css sass support server pages should support sass/scss modules inside server pages"
],
"failed": [
"app dir - css HMR should not create duplicate link tags during HMR",
Turbopack: switch to a single client components entrypoint (#59352) ### What? switch turbopack to use a single client components entrypoint for all client components on a page for development. This aligns it with the webpack behavior. ### Why? compiling a separate entrypoint for every client component is pretty expensive in regards of compilation, chunking, code generation, file writing and number of requests. ### Turbopack Changes * https://github.com/vercel/turbo/pull/6713 <!-- Tobias Koppers - use real emojis --> * https://github.com/vercel/turbo/pull/6728 <!-- Tobias Koppers - fix order of reverse topologic iteration --> Closes PACK-2115
2023-12-08 08:24:08 +01:00
"app dir - css Suspensey CSS should suspend on CSS imports if its slow on client navigation",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - css css support chunks should bundle css resources into chunks",
"app dir - css css support multiple entries should only include the same style once in the flight data",
"app dir - css css support should not preload styles twice during HMR",
"app dir - css css support special entries should include css imported in loading.js"
],
"pending": [
"app dir - css css support multiple entries should only inject the same style once if used by different layers",
"app dir - css css support multiple entries should only load chunks for the css module that is used by the specific entrypoint",
"app dir - css css support server layouts should support global css inside server layouts"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"flakey": [
"app dir - css css support server layouts should support external css imports"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"test/e2e/app-dir/app-custom-cache-handler/index.test.ts": {
"passed": [
"app-dir - custom-cache-handler - cjs cjs module exports should have logs from cache-handler",
"app-dir - custom-cache-handler - cjs-default-export cjs default export should have logs from cache-handler",
"app-dir - custom-cache-handler - esm esm default export should have logs from cache-handler"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-edge-root-layout/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir edge runtime root layout should not emit metadata files into bad paths"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-edge/app-edge.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir edge SSR should handle /index routes correctly",
"app-dir edge SSR should handle edge only routes",
"app-dir edge SSR should handle edge rsc hmr",
update manifest (#56737) ### What? updates from daily test run Closes WEB-1766
2023-10-13 11:19:54 +02:00
"app-dir edge SSR should resolve client component without error",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app-dir edge SSR should resolve module without error in edge runtime",
"app-dir edge SSR should retrieve cookies in a server component in the edge runtime"
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir edge SSR should warn about the re-export of a pages runtime/preferredRegion config"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"test/e2e/app-dir/app-esm-js/index.test.ts": {
"passed": [
"app-dir - esm js extension should be able to render nextjs api in app router",
"app-dir - esm js extension should be able to use nextjs api in pages router"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-external/app-external.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"app dir - external dependency mixed syntax external modules should handle mixed module in server and client components",
"app dir - external dependency mixed syntax external modules should handle mixed module with next/dynamic",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - external dependency react in external esm packages should use the same react in client app",
"app dir - external dependency react in external esm packages should use the same react in edge server app",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"app dir - external dependency react in external esm packages should use the same react in pages",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - external dependency react in external esm packages should use the same react in server app",
Update Turbopack test manifest (#60413) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-09 10:32:10 +01:00
"app dir - external dependency server actions should not prefer to resolve esm over cjs for bundling optout packages",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - external dependency should correctly collect global css imports and mark them as side effects",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"app dir - external dependency should emit cjs helpers for external cjs modules when compiled",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - external dependency should export client module references in esm",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - external dependency should handle external async module libraries correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - external dependency should handle external css modules",
"app dir - external dependency should handle external css modules in pages",
"app dir - external dependency should handle external next/font",
"app dir - external dependency should resolve 3rd party package exports based on the react-server condition",
"app dir - external dependency should resolve the subset react in server components based on the react-server condition",
"app dir - external dependency should support exporting multiple star re-exports",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - external dependency should transpile specific external packages with the `transpilePackages` option",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - external dependency should use the same async storages if imported directly",
"app dir - external dependency should use the same export type for packages in both ssr and client"
],
"failed": [
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"app dir - external dependency server actions should compile server actions from node_modules in client components",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - external dependency should be able to opt-out 3rd party packages being bundled in server components",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"app dir - external dependency should have proper tree-shaking for known modules in CJS"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-fetch-deduping/app-fetch-deduping.test.ts": {
"passed": [
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"app-fetch-deduping during next dev should dedupe pending revalidation requests",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app-fetch-deduping during next dev should dedupe requests called from the same component"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"test/e2e/app-dir/app-invalid-revalidate/app-invalid-revalidate.test.ts": {
"passed": [
"app-invalid-revalidate should error properly for invalid revalidate at layout",
"app-invalid-revalidate should error properly for invalid revalidate at page",
"app-invalid-revalidate should error properly for invalid revalidate on fetch",
"app-invalid-revalidate should error properly for invalid revalidate on unstable_cache"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-middleware/app-middleware.test.ts": {
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"passed": [
fix(next-core): allow runtime segment option in pages/api (#58409) ### What This PR fixes turbopack to allow runtime segment option (https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes#segment-runtime-Option) in pages/api. Previously it only allows config object (https://nextjs.org/docs/app/building-your-application/routing/middleware#matcher), so the single runtime export like `export const runtime = 'edge'` didn't work. PR updates logic to parse config in the module to allow single segment export as well. It doesn't allow _both_, if config object is exported it'll short-curcuit to read values as config object should able to specify runtime without separate runtime segment. Closes PACK-1961
2023-11-17 21:59:01 +01:00
"app dir - middleware with middleware in src dir works without crashing when using requestAsyncStorage",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"app dir - middleware without pages dir Updates headers",
"app-dir with middleware Mutate request headers for Edge Functions Adds new headers",
"app-dir with middleware Mutate request headers for Edge Functions Deletes headers",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir with middleware Mutate request headers for Edge Functions Supports draft mode",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"app-dir with middleware Mutate request headers for Edge Functions Updates headers",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir with middleware Mutate request headers for Serverless Functions Adds new headers",
"app-dir with middleware Mutate request headers for Serverless Functions Deletes headers",
"app-dir with middleware Mutate request headers for Serverless Functions Supports draft mode",
"app-dir with middleware Mutate request headers for Serverless Functions Updates headers",
"app-dir with middleware Mutate request headers for next/headers Adds new headers",
"app-dir with middleware Mutate request headers for next/headers Deletes headers",
"app-dir with middleware Mutate request headers for next/headers Supports draft mode",
"app-dir with middleware Mutate request headers for next/headers Updates headers",
fix(next-core): allow runtime segment option in pages/api (#58409) ### What This PR fixes turbopack to allow runtime segment option (https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes#segment-runtime-Option) in pages/api. Previously it only allows config object (https://nextjs.org/docs/app/building-your-application/routing/middleware#matcher), so the single runtime export like `export const runtime = 'edge'` didn't work. PR updates logic to parse config in the module to allow single segment export as well. It doesn't allow _both_, if config object is exported it'll short-curcuit to read values as config object should able to specify runtime without separate runtime segment. Closes PACK-1961
2023-11-17 21:59:01 +01:00
"app-dir with middleware should filter correctly after middleware rewrite"
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
],
fix(next-core): allow runtime segment option in pages/api (#58409) ### What This PR fixes turbopack to allow runtime segment option (https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes#segment-runtime-Option) in pages/api. Previously it only allows config object (https://nextjs.org/docs/app/building-your-application/routing/middleware#matcher), so the single runtime export like `export const runtime = 'edge'` didn't work. PR updates logic to parse config in the module to allow single segment export as well. It doesn't allow _both_, if config object is exported it'll short-curcuit to read values as config object should able to specify runtime without separate runtime segment. Closes PACK-1961
2023-11-17 21:59:01 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"test/e2e/app-dir/app-prefetch-false-loading/app-prefetch-false-loading.test.ts": {
"passed": [
"app-prefetch-false-loading should not re-trigger loading state when navigating between pages that share a dynamic layout",
"app-prefetch-false-loading should render loading for the inital render"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-prefetch-false/app-prefetch-false.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": ["app-prefetch-false should skip test in dev mode"],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"test/e2e/app-dir/app-prefetch-static/app-prefetch-static.test.ts": {
"passed": ["app-prefetch-static should skip next dev"],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-prefetch/prefetching.test.ts": {
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"passed": ["app dir - prefetching should skip next dev for now"],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-rendering/rendering.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir rendering ISR should revalidate the page when revalidate is configured",
"app dir rendering SSR only should run data fetch in parallel",
"app dir rendering SSR only should run data in layout and page",
"app dir rendering should serve app/page.server.js at /",
"app dir rendering static only should run data in layout and page",
"app dir rendering static only should run data in parallel during development"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [
"app dir rendering mixed static and dynamic should generate static data during build and use it"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-routes-trailing-slash/app-routes-trailing-slash.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-routes-trailing-slash should handle trailing slash for edge runtime",
"app-routes-trailing-slash should handle trailing slash for node runtime"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-routes/app-custom-route-base-path.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-custom-routes automatic implementations implements HEAD on routes with GET already implemented",
"app-custom-routes automatic implementations implements OPTIONS on routes",
"app-custom-routes basic fetch request with a response made via a DELETE request responds correctly on /basic/endpoint",
"app-custom-routes basic fetch request with a response made via a DELETE request responds correctly on /basic/vercel/endpoint",
"app-custom-routes basic fetch request with a response made via a GET request responds correctly on /basic/endpoint",
"app-custom-routes basic fetch request with a response made via a GET request responds correctly on /basic/vercel/endpoint",
"app-custom-routes basic fetch request with a response made via a PATCH request responds correctly on /basic/endpoint",
"app-custom-routes basic fetch request with a response made via a PATCH request responds correctly on /basic/vercel/endpoint",
"app-custom-routes basic fetch request with a response made via a POST request responds correctly on /basic/endpoint",
"app-custom-routes basic fetch request with a response made via a POST request responds correctly on /basic/vercel/endpoint",
"app-custom-routes basic fetch request with a response made via a PUT request responds correctly on /basic/endpoint",
"app-custom-routes basic fetch request with a response made via a PUT request responds correctly on /basic/vercel/endpoint",
"app-custom-routes basic fetch request with a response request can read query parameters",
"app-custom-routes basic fetch request with a response request can read query parameters (edge)",
"app-custom-routes basic fetch request with a response response supports the NextResponse.json() helper",
"app-custom-routes basic fetch request with a response response supports the NextResponse.redirect() helper",
"app-custom-routes basic fetch request with a response route groups routes to the correct handler",
"app-custom-routes body can handle handle a streaming request and streaming response",
"app-custom-routes body can handle handle a streaming request and streaming response (edge)",
"app-custom-routes body can read a JSON encoded body",
"app-custom-routes body can read a JSON encoded body (edge)",
"app-custom-routes body can read a JSON encoded body for DELETE requests",
"app-custom-routes body can read a JSON encoded body for OPTIONS requests",
"app-custom-routes body can read a streamed JSON encoded body",
"app-custom-routes body can read a streamed JSON encoded body (edge)",
"app-custom-routes body can read the text body",
"app-custom-routes body can read the text body (edge)",
"app-custom-routes context does not provide params to routes without dynamic parameters",
"app-custom-routes context provides params to routes with catch-all routes",
"app-custom-routes context provides params to routes with dynamic parameters",
"app-custom-routes customized metadata routes should work if conflict with metadata routes convention",
"app-custom-routes dynamic = \"force-static\" strips search, headers, and domain from request",
"app-custom-routes edge functions returns a response when headers are accessed",
"app-custom-routes edge functions returns response using edge runtime",
"app-custom-routes error conditions responds with 400 (Bad Request) when the requested method is not a valid HTTP method",
"app-custom-routes error conditions responds with 405 (Method Not Allowed) when method is not implemented",
"app-custom-routes error conditions responds with 500 (Internal Server Error) when the handler calls NextResponse.next()",
"app-custom-routes error conditions responds with 500 (Internal Server Error) when the handler throws an error",
"app-custom-routes hooks cookies gets the correct values",
"app-custom-routes hooks cookies().has() gets the correct values",
"app-custom-routes hooks headers gets the correct values",
"app-custom-routes hooks notFound can respond correctly",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app-custom-routes hooks permanentRedirect can respond correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-custom-routes hooks redirect can respond correctly",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"app-custom-routes hooks req.cookies gets the correct values",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app-custom-routes invalid exports should print an error when exporting a default handler in dev",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-custom-routes no response returned should print an error when no response is returned",
"app-custom-routes works with api prefix correctly does not statically generate with dynamic usage",
"app-custom-routes works with api prefix correctly statically generates correctly with no dynamic usage",
"app-custom-routes works with generateStaticParams correctly responds correctly on /static/first/data.json",
"app-custom-routes works with generateStaticParams correctly responds correctly on /static/second/data.json",
"app-custom-routes works with generateStaticParams correctly responds correctly on /static/three/data.json",
"app-custom-routes works with generateStaticParams correctly revalidates correctly on /revalidate-1/first/data.json",
"app-custom-routes works with generateStaticParams correctly revalidates correctly on /revalidate-1/second/data.json",
"app-custom-routes works with generateStaticParams correctly revalidates correctly on /revalidate-1/three/data.json"
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [
"app-custom-routes basic fetch request with a response response supports the NextResponse.rewrite() helper"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-routes/app-custom-routes.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-custom-routes automatic implementations implements HEAD on routes with GET already implemented",
"app-custom-routes automatic implementations implements OPTIONS on routes",
"app-custom-routes basic fetch request with a response made via a DELETE request responds correctly on /basic/endpoint",
"app-custom-routes basic fetch request with a response made via a DELETE request responds correctly on /basic/vercel/endpoint",
"app-custom-routes basic fetch request with a response made via a GET request responds correctly on /basic/endpoint",
"app-custom-routes basic fetch request with a response made via a GET request responds correctly on /basic/vercel/endpoint",
"app-custom-routes basic fetch request with a response made via a PATCH request responds correctly on /basic/endpoint",
"app-custom-routes basic fetch request with a response made via a PATCH request responds correctly on /basic/vercel/endpoint",
"app-custom-routes basic fetch request with a response made via a POST request responds correctly on /basic/endpoint",
"app-custom-routes basic fetch request with a response made via a POST request responds correctly on /basic/vercel/endpoint",
"app-custom-routes basic fetch request with a response made via a PUT request responds correctly on /basic/endpoint",
"app-custom-routes basic fetch request with a response made via a PUT request responds correctly on /basic/vercel/endpoint",
"app-custom-routes basic fetch request with a response request can read query parameters",
"app-custom-routes basic fetch request with a response request can read query parameters (edge)",
"app-custom-routes basic fetch request with a response response supports the NextResponse.json() helper",
"app-custom-routes basic fetch request with a response response supports the NextResponse.redirect() helper",
"app-custom-routes basic fetch request with a response route groups routes to the correct handler",
"app-custom-routes body can handle handle a streaming request and streaming response",
"app-custom-routes body can handle handle a streaming request and streaming response (edge)",
"app-custom-routes body can read a JSON encoded body",
"app-custom-routes body can read a JSON encoded body (edge)",
"app-custom-routes body can read a JSON encoded body for DELETE requests",
"app-custom-routes body can read a JSON encoded body for OPTIONS requests",
"app-custom-routes body can read a streamed JSON encoded body",
"app-custom-routes body can read a streamed JSON encoded body (edge)",
"app-custom-routes body can read the text body",
"app-custom-routes body can read the text body (edge)",
"app-custom-routes context does not provide params to routes without dynamic parameters",
"app-custom-routes context provides params to routes with catch-all routes",
"app-custom-routes context provides params to routes with dynamic parameters",
"app-custom-routes customized metadata routes should work if conflict with metadata routes convention",
"app-custom-routes dynamic = \"force-static\" strips search, headers, and domain from request",
"app-custom-routes edge functions returns a response when headers are accessed",
"app-custom-routes edge functions returns response using edge runtime",
"app-custom-routes error conditions responds with 400 (Bad Request) when the requested method is not a valid HTTP method",
"app-custom-routes error conditions responds with 405 (Method Not Allowed) when method is not implemented",
"app-custom-routes error conditions responds with 500 (Internal Server Error) when the handler calls NextResponse.next()",
"app-custom-routes error conditions responds with 500 (Internal Server Error) when the handler throws an error",
"app-custom-routes hooks cookies gets the correct values",
"app-custom-routes hooks cookies().has() gets the correct values",
"app-custom-routes hooks headers gets the correct values",
"app-custom-routes hooks notFound can respond correctly",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app-custom-routes hooks permanentRedirect can respond correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-custom-routes hooks redirect can respond correctly",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"app-custom-routes hooks req.cookies gets the correct values",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app-custom-routes invalid exports should print an error when exporting a default handler in dev",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-custom-routes no response returned should print an error when no response is returned",
"app-custom-routes works with api prefix correctly does not statically generate with dynamic usage",
"app-custom-routes works with api prefix correctly statically generates correctly with no dynamic usage",
"app-custom-routes works with generateStaticParams correctly responds correctly on /static/first/data.json",
"app-custom-routes works with generateStaticParams correctly responds correctly on /static/second/data.json",
"app-custom-routes works with generateStaticParams correctly responds correctly on /static/three/data.json",
"app-custom-routes works with generateStaticParams correctly revalidates correctly on /revalidate-1/first/data.json",
"app-custom-routes works with generateStaticParams correctly revalidates correctly on /revalidate-1/second/data.json",
"app-custom-routes works with generateStaticParams correctly revalidates correctly on /revalidate-1/three/data.json"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [
"app-custom-routes basic fetch request with a response response supports the NextResponse.rewrite() helper"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-simple-routes/app-simple-routes.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-simple-routes works with simple routes renders a edge route",
"app-simple-routes works with simple routes renders a node route"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-static/app-static-custom-handler.test.ts": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should allow dynamic routes to access cookies",
"app-dir static/dynamic handling should bypass fetch cache with cache-control: no-cache",
"app-dir static/dynamic handling should cache correctly for cache: no-store",
"app-dir static/dynamic handling should cache correctly for fetchCache = default-cache",
"app-dir static/dynamic handling should cache correctly for fetchCache = force-cache",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app-dir static/dynamic handling should cache correctly handle JSON body",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should cache correctly with POST method and revalidate",
"app-dir static/dynamic handling should cache correctly with authorization header and revalidate",
"app-dir static/dynamic handling should cache correctly with cookie header and revalidate",
"app-dir static/dynamic handling should cache correctly with post method and revalidate",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app-dir static/dynamic handling should cache correctly with post method and revalidate edge",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should cache correctly with utf8 encoding",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app-dir static/dynamic handling should cache correctly with utf8 encoding edge",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should correctly handle fetchCache = \"force-no-store\"",
"app-dir static/dynamic handling should correctly handle multi-level generateStaticParams when some levels are missing",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"app-dir static/dynamic handling should correctly handle statusCode with notFound + ISR",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should correctly include headers instance in cache key",
"app-dir static/dynamic handling should correctly skip caching POST fetch for POST handler",
"app-dir static/dynamic handling should error correctly for invalid params from generateStaticParams",
"app-dir static/dynamic handling should force SSR correctly for headers usage",
"app-dir static/dynamic handling should handle dynamicParams: false correctly",
"app-dir static/dynamic handling should handle dynamicParams: true correctly",
"app-dir static/dynamic handling should handle partial-gen-params with default dynamicParams correctly",
"app-dir static/dynamic handling should handle partial-gen-params with layout dynamicParams = false correctly",
"app-dir static/dynamic handling should handle partial-gen-params with page dynamicParams = false correctly",
"app-dir static/dynamic handling should have logs from cache-handler",
"app-dir static/dynamic handling should honor fetch cache correctly",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app-dir static/dynamic handling should honor fetch cache correctly (edge)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should keep querystring on static page",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"app-dir static/dynamic handling should load large data only once when using custom cache handler and force-cache mode",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should navigate to static path correctly",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app-dir static/dynamic handling should not cache correctly with POST method request init",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should not cache non-ok statusCode",
"app-dir static/dynamic handling should not error with force-dynamic and catch-all routes",
"app-dir static/dynamic handling should not error with generateStaticParams and authed data on revalidate",
"app-dir static/dynamic handling should not error with generateStaticParams and dynamic data",
"app-dir static/dynamic handling should not have cache tags header for non-minimal mode",
"app-dir static/dynamic handling should not throw Dynamic Server Usage error when using generateStaticParams with draftMode",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"app-dir static/dynamic handling should render not found pages correctly and fallback to the default one",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should skip cache in draft mode",
"app-dir static/dynamic handling should ssr dynamically when detected automatically with fetch cache option",
"app-dir static/dynamic handling should ssr dynamically when forced via config",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"app-dir static/dynamic handling should stream properly for /stale-cache-serving-edge/app-page",
"app-dir static/dynamic handling should stream properly for /stale-cache-serving-edge/route-handler",
"app-dir static/dynamic handling should stream properly for /stale-cache-serving/app-page",
"app-dir static/dynamic handling should stream properly for /stale-cache-serving/route-handler",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should work with dynamic path no generateStaticParams",
"app-dir static/dynamic handling should work with forced dynamic path",
"app-dir static/dynamic handling unstable-cache should work in pages/api/unstable-cache-edge",
"app-dir static/dynamic handling unstable-cache should work in pages/api/unstable-cache-node",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app-dir static/dynamic handling unstable-cache should work in pages/unstable-cache-edge",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling unstable-cache should work in pages/unstable-cache-node",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"app-dir static/dynamic handling unstable_noStore should not opt-out of static optimization when used in next/cache",
"app-dir static/dynamic handling unstable_noStore should opt-out of static optimization",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling usePathname should have the correct values",
"app-dir static/dynamic handling usePathname should have values from canonical url on rewrite",
"app-dir static/dynamic handling useSearchParams client should bailout to client rendering - with suspense boundary",
"app-dir static/dynamic handling useSearchParams client should bailout to client rendering - without suspense boundary",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app-dir static/dynamic handling useSearchParams client should have values from canonical url on rewrite"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [
"app-dir static/dynamic handling should correctly de-dupe fetch without next cache /react-fetch-deduping-edge",
"app-dir static/dynamic handling should correctly de-dupe fetch without next cache /react-fetch-deduping-node",
"app-dir static/dynamic handling should ssr dynamically when detected automatically with fetch revalidate option",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app-dir static/dynamic handling useSearchParams client should have empty search params on force-static"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-static/app-static.test.ts": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling it should revalidate tag correctly with edge route handler",
"app-dir static/dynamic handling it should revalidate tag correctly with node route handler",
"app-dir static/dynamic handling should allow dynamic routes to access cookies",
"app-dir static/dynamic handling should bypass fetch cache with cache-control: no-cache",
"app-dir static/dynamic handling should cache correctly for cache: no-store",
"app-dir static/dynamic handling should cache correctly for fetchCache = default-cache",
"app-dir static/dynamic handling should cache correctly for fetchCache = force-cache",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app-dir static/dynamic handling should cache correctly handle JSON body",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should cache correctly with POST method and revalidate",
"app-dir static/dynamic handling should cache correctly with authorization header and revalidate",
"app-dir static/dynamic handling should cache correctly with cookie header and revalidate",
"app-dir static/dynamic handling should cache correctly with post method and revalidate",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app-dir static/dynamic handling should cache correctly with post method and revalidate edge",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should cache correctly with utf8 encoding",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app-dir static/dynamic handling should cache correctly with utf8 encoding edge",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should correctly handle fetchCache = \"force-no-store\"",
"app-dir static/dynamic handling should correctly handle multi-level generateStaticParams when some levels are missing",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"app-dir static/dynamic handling should correctly handle statusCode with notFound + ISR",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should correctly include headers instance in cache key",
"app-dir static/dynamic handling should correctly skip caching POST fetch for POST handler",
"app-dir static/dynamic handling should error correctly for invalid params from generateStaticParams",
"app-dir static/dynamic handling should force SSR correctly for headers usage",
"app-dir static/dynamic handling should handle dynamicParams: false correctly",
"app-dir static/dynamic handling should handle dynamicParams: true correctly",
"app-dir static/dynamic handling should handle partial-gen-params with default dynamicParams correctly",
"app-dir static/dynamic handling should handle partial-gen-params with layout dynamicParams = false correctly",
"app-dir static/dynamic handling should handle partial-gen-params with page dynamicParams = false correctly",
"app-dir static/dynamic handling should honor dynamic = \"force-static\" correctly",
"app-dir static/dynamic handling should honor dynamic = \"force-static\" correctly (lazy)",
"app-dir static/dynamic handling should honor fetch cache correctly",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app-dir static/dynamic handling should honor fetch cache correctly (edge)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should honor fetch cache in generateStaticParams",
"app-dir static/dynamic handling should keep querystring on static page",
"app-dir static/dynamic handling should navigate to static path correctly",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app-dir static/dynamic handling should not cache correctly with POST method request init",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should not cache non-ok statusCode",
"app-dir static/dynamic handling should not error with force-dynamic and catch-all routes",
"app-dir static/dynamic handling should not error with generateStaticParams and authed data on revalidate",
"app-dir static/dynamic handling should not error with generateStaticParams and dynamic data",
"app-dir static/dynamic handling should not have cache tags header for non-minimal mode",
"app-dir static/dynamic handling should not throw Dynamic Server Usage error when using generateStaticParams with draftMode",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"app-dir static/dynamic handling should render not found pages correctly and fallback to the default one",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should revalidate correctly with config and fetch revalidate",
"app-dir static/dynamic handling should skip cache in draft mode",
"app-dir static/dynamic handling should ssr dynamically when detected automatically with fetch cache option",
"app-dir static/dynamic handling should ssr dynamically when forced via config",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"app-dir static/dynamic handling should stream properly for /stale-cache-serving-edge/app-page",
"app-dir static/dynamic handling should stream properly for /stale-cache-serving-edge/route-handler",
"app-dir static/dynamic handling should stream properly for /stale-cache-serving/app-page",
"app-dir static/dynamic handling should stream properly for /stale-cache-serving/route-handler",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should work with dynamic path no generateStaticParams",
"app-dir static/dynamic handling should work with forced dynamic path",
"app-dir static/dynamic handling unstable-cache should work in pages/api/unstable-cache-edge",
"app-dir static/dynamic handling unstable-cache should work in pages/api/unstable-cache-node",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app-dir static/dynamic handling unstable-cache should work in pages/unstable-cache-edge",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling unstable-cache should work in pages/unstable-cache-node",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"app-dir static/dynamic handling unstable_noStore should not opt-out of static optimization when used in next/cache",
"app-dir static/dynamic handling unstable_noStore should opt-out of static optimization",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling usePathname should have the correct values",
"app-dir static/dynamic handling usePathname should have values from canonical url on rewrite",
"app-dir static/dynamic handling useSearchParams client should bailout to client rendering - with suspense boundary",
"app-dir static/dynamic handling useSearchParams client should bailout to client rendering - without suspense boundary",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app-dir static/dynamic handling useSearchParams client should have values from canonical url on rewrite"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir static/dynamic handling should correctly de-dupe fetch without next cache /react-fetch-deduping-edge",
"app-dir static/dynamic handling should correctly de-dupe fetch without next cache /react-fetch-deduping-node",
"app-dir static/dynamic handling should ssr dynamically when detected automatically with fetch revalidate option",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app-dir static/dynamic handling useSearchParams client should have empty search params on force-static"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app-validation/validation.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - validation should error when passing invalid router state tree"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"test/e2e/app-dir/app/experimental-compile.test.ts": {
"passed": ["should skip"],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
update manifest (#56737) ### What? updates from daily test run Closes WEB-1766
2023-10-13 11:19:54 +02:00
"app dir - basic <Link /> should allow linking from app page to pages page",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"app dir - basic <Link /> should be soft for back navigation",
"app dir - basic <Link /> should be soft for forward navigation",
"app dir - basic <Link /> should hard push",
"app dir - basic <Link /> should hard replace",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - basic <Link /> should navigate to pages dynamic route from pages page if it overlaps with an app page",
"app dir - basic <Link /> should push to external url",
"app dir - basic <Link /> should replace to external url",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"app dir - basic <Link /> should soft push",
"app dir - basic HMR should HMR correctly for client component",
"app dir - basic HMR should HMR correctly for server component",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - basic bootstrap scripts should only bootstrap with one script, prinitializing the rest",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"app dir - basic bootstrap scripts should successfully bootstrap even when using CSP",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - basic data fetch with response over 16KB with chunked encoding should load page when fetching a large amount of data",
"app dir - basic error component should display error digest for error in server component with default error boundary",
"app dir - basic error component should trigger error component when an error happens during rendering",
"app dir - basic error component should trigger error component when an error happens during server components rendering",
"app dir - basic error component should use default error boundary for prod and overlay for dev when no error component specified",
"app dir - basic known bugs should handle as on next/link",
"app dir - basic known bugs should handle next/link back to initially loaded page",
"app dir - basic known bugs should handle router.refresh without resetting state",
"app dir - basic known bugs should not do additional pushState when already on the page",
"app dir - basic known bugs should not share flight data between requests",
"app dir - basic known bugs should support React cache client component",
"app dir - basic known bugs should support React cache client component client-navigation",
"app dir - basic known bugs should support React cache middleware overriding headers",
"app dir - basic known bugs should support React cache server component",
"app dir - basic known bugs should support React cache server component client-navigation",
"app dir - basic known bugs should support React fetch instrumentation server component",
"app dir - basic known bugs should support React fetch instrumentation server component client-navigation",
"app dir - basic next/script should insert preload tags for beforeInteractive and afterInteractive scripts",
"app dir - basic next/script should load stylesheets for next/scripts",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"app dir - basic next/script should pass on extra props for beforeInteractive scripts with a src prop",
"app dir - basic next/script should pass on extra props for beforeInteractive scripts without a src prop",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - basic next/script should support next/script and render in correct order",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - basic rewrites should support rewrites on client-side navigation",
"app dir - basic rewrites should support rewrites on client-side navigation from pages to app with existing pages path",
"app dir - basic rewrites should support rewrites on initial load",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - basic searchParams prop client component should have the correct search params",
"app dir - basic searchParams prop client component should have the correct search params on middleware rewrite",
"app dir - basic searchParams prop client component should have the correct search params on rewrite",
"app dir - basic searchParams prop server component should have the correct search params",
"app dir - basic searchParams prop server component should have the correct search params on middleware rewrite",
"app dir - basic searchParams prop server component should have the correct search params on rewrite",
"app dir - basic server components Loading should render loading.js in browser for slow layout",
"app dir - basic server components Loading should render loading.js in browser for slow layout and page",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - basic server components Loading should render loading.js in browser for slow page",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - basic server components Loading should render loading.js in initial html for slow layout",
"app dir - basic server components Loading should render loading.js in initial html for slow layout and page",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - basic server components Loading should render loading.js in initial html for slow page",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - basic server components catch-all routes should handle catch-all segments link",
"app dir - basic server components catch-all routes should handle optional catch-all segments link",
"app dir - basic server components catch-all routes should handle optional segments",
"app dir - basic server components catch-all routes should handle optional segments root",
"app dir - basic server components catch-all routes should handle required segments",
"app dir - basic server components catch-all routes should handle required segments root as not found",
"app dir - basic server components client components should have consistent query and params handling",
"app dir - basic server components dynamic routes should only pass params that apply to the layout",
"app dir - basic server components middleware should strip internal query parameters from requests to middleware for redirect",
"app dir - basic server components middleware should strip internal query parameters from requests to middleware for rewrite",
"app dir - basic server components next/router should support router.back and router.forward",
"app dir - basic server components should include client component layout with server component route should include it client-side",
"app dir - basic server components should include client component layout with server component route should include it server-side",
"app dir - basic server components should not serve .client.js as a path",
"app dir - basic server components should not serve .server.js as a path",
"app dir - basic server components should serve client component should serve client-side",
"app dir - basic server components should serve client component should serve server-side",
"app dir - basic server components should serve shared component",
"app dir - basic should ensure the </body></html> suffix is at the end of the stream",
"app dir - basic should handle hash in initial url",
"app dir - basic should have correct searchParams and params (client)",
"app dir - basic should have correct searchParams and params (server)",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - basic should include document html and body",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - basic should include layouts when no direct parent layout",
"app dir - basic should include parent document when no direct parent layout",
"app dir - basic should match redirects in pages correctly $path",
"app dir - basic should not apply client router filter on shallow",
"app dir - basic should not create new root layout when nested (optional)",
"app dir - basic should not have duplicate config warnings",
"app dir - basic should not include parent when not in parent directory",
"app dir - basic should not serve when layout is provided but no folder index",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - basic should not share edge workers",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - basic should pass props from getServerSideProps in root layout",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"app dir - basic should return normalized dynamic route params for catch-all edge page",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - basic should return the `vary` header from edge runtime",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - basic should return the `vary` header from pages for flight requests",
"app dir - basic should serve /index as separate page",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - basic should serve dynamic parameter",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - basic should serve dynamic route from pages",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - basic should serve from app",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - basic should serve from pages",
"app dir - basic should serve from public",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - basic should serve nested parent",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - basic should serve page as a segment name correctly",
"app dir - basic should use new root layout when provided",
"app dir - basic should use text/x-component for flight",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"app dir - basic should use text/x-component for flight with edge runtime",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - basic should work for catch-all edge page",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - basic template component should render the template that holds state in a client component and reset on navigation"
],
"failed": [
"app dir - basic should encode chunk path correctly",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"app dir - basic should serve polyfills for browsers that do not support modules"
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
],
"pending": [
"app dir - basic <Link /> should soft replace",
"app dir - basic HMR should HMR correctly when changing the component type",
"app dir - basic known bugs should support React fetch instrumentation client component",
"app dir - basic known bugs should support React fetch instrumentation client component client-navigation",
"app dir - basic should handle css imports in next/dynamic correctly",
"app dir - basic should match partial parameters",
"app dir - basic should not include parent when not in parent directory with route in directory",
"app dir - basic should not rerender layout when navigating between routes in the same layout",
"app dir - basic template component should render the template that is a server component and rerender on navigation"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"runtimeError": false
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
},
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"test/e2e/app-dir/app/standalone-gsp.test.ts": {
"passed": ["should skip for non-next start"],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app/standalone.test.ts": {
"passed": ["should skip for non-next start"],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/app/useReportWebVitals.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"useReportWebVitals hook should send web-vitals to vercel-insights"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"runtimeError": false
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
},
"test/e2e/app-dir/app/vercel-speed-insights.test.ts": {
"passed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"vercel speed insights with assetPrefix Vercel analytics should send web vitals to Vercel analytics",
"vercel speed insights without assetPrefix Vercel analytics should send web vitals to Vercel analytics"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/asset-prefix/asset-prefix.test.ts": {
"passed": [
"app-dir assetPrefix handling should redirect route when clicking link",
"app-dir assetPrefix handling should redirect route when requesting it directly",
"app-dir assetPrefix handling should redirect route when requesting it directly by browser",
"app-dir assetPrefix handling should render link"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/async-component-preload/async-component-preload.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"async-component-preload should handle redirect in an async page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/e2e/app-dir/autoscroll-with-css-modules/index.test.ts": {
"passed": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"router autoscrolling on navigation with css modules vertical scroll when page imports css modules should scroll to top of document when navigating between to pages without layout when",
"router autoscrolling on navigation with css modules vertical scroll when page imports css modules should scroll when clicking in JS"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/e2e/app-dir/back-button-download-bug/back-button-download-bug.test.ts": {
"passed": [],
"failed": [],
"pending": [
"app-dir back button download bug app-dir back button download bug should redirect route when clicking link"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/e2e/app-dir/build-size/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": ["app-dir build size should skip next dev for now"],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"test/e2e/app-dir/conflicting-page-segments/conflicting-page-segments.test.ts": {
"passed": [],
"failed": [
"conflicting-page-segments should throw an error when a route groups causes a conflict with a parallel segment"
],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/create-root-layout/create-root-layout.test.ts": {
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir create root layout page.js find available dir create root layout",
"app-dir create root layout page.js root layout in app create root layout",
"app-dir create root layout page.js root layout in route group create root layout",
"app-dir create root layout page.tsx create root layout"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/crypto-globally-available/crypto-globally-available.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Web Crypto API is available globally should be available in Route Handlers",
"Web Crypto API is available globally should be available in Server Components"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/draft-mode/draft-mode.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - draft mode in edge runtime should be disabled from api route handler",
"app dir - draft mode in edge runtime should be enabled from api route handler when draft mode enabled",
"app dir - draft mode in edge runtime should have set-cookie header on enable",
"app dir - draft mode in edge runtime should have set-cookie header with redirect location",
"app dir - draft mode in edge runtime should not perform full page navigation on router.refresh()",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - draft mode in edge runtime should use initial rand when draft mode is disabled on /with-edge/index",
"app dir - draft mode in edge runtime should use initial rand when draft mode is disabled on /with-edge/with-cookies",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - draft mode in nodejs runtime should be disabled from api route handler",
"app dir - draft mode in nodejs runtime should be enabled from api route handler when draft mode enabled",
"app dir - draft mode in nodejs runtime should genenerate rand when draft mode enabled",
"app dir - draft mode in nodejs runtime should have set-cookie header on enable",
"app dir - draft mode in nodejs runtime should have set-cookie header with redirect location",
"app dir - draft mode in nodejs runtime should not perform full page navigation on router.refresh()",
"app dir - draft mode in nodejs runtime should read other cookies when draft mode enabled",
"app dir - draft mode in nodejs runtime should use initial rand when draft mode is disabled on /index",
"app dir - draft mode in nodejs runtime should use initial rand when draft mode is disabled on /with-cookies"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [
"app dir - draft mode in edge runtime should genenerate rand when draft mode enabled",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - draft mode in edge runtime should read other cookies when draft mode enabled"
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/dynamic-href/dynamic-href.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"dynamic-href should error when using dynamic href in app dir",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"dynamic-href should error when using dynamic href.pathname in app dir"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/dynamic/dynamic.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"app dir - next/dynamic no SSR should not render client component imported through ssr: false in client components",
"app dir - next/dynamic no SSR should not render client component imported through ssr: false in client components in edge runtime",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - next/dynamic should generate correct client manifest for dynamic chunks",
"app dir - next/dynamic should handle next/dynamic in SSR correctly",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"app dir - next/dynamic should handle next/dynamic in hydration correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - next/dynamic should handle ssr: false in pages when appDir is enabled"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#59356) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-07 15:51:45 +01:00
"test/e2e/app-dir/edge-route-catchall/edge-route-catchall.test.ts": {
"passed": [
"edge-route-catchall should correctly normalize edge route catch-all with a single param",
"edge-route-catchall should correctly normalize edge route catch-all with multiple params"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"test/e2e/app-dir/edge-route-rewrite/edge-route-rewrite.test.ts": {
"passed": [
"edge-route-rewrite it should support a rewrite to a dynamic edge route",
"edge-route-rewrite it should support a rewrite to an edge route"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/edge-runtime-node-compatibility/edge-runtime-node-compatibility.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"edge runtime node compatibility [app] supports node:buffer",
"edge runtime node compatibility [pages/api] supports node:buffer"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/emotion-js/index.test.ts": {
test(turbopack): update test manifest (#57366) ### What Enabling test from https://github.com/vercel/next.js/pull/57300. There may be some other test cases passing by fix, but this is the known direct offending test can be enabled. Closes WEB-1847
2023-10-24 23:55:38 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - emotion-js should render emotion-js css with compiler.emotion option correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
test(turbopack): update test manifest (#57366) ### What Enabling test from https://github.com/vercel/next.js/pull/57300. There may be some other test cases passing by fix, but this is the known direct offending test can be enabled. Closes WEB-1847
2023-10-24 23:55:38 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/error-boundary-navigation/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - not found navigation should allow navigating to a non-existent page",
"app dir - not found navigation should allow navigating to a page calling notfound",
"app dir - not found navigation should allow navigation back to route that was initially not-found",
"app dir - not found navigation should allow navigation on error",
"app dir - not found navigation should allow navigation on not-found",
"app dir - not found navigation should allow navigation to other routes on route that was initially not-found",
"app dir - not found navigation should be able to navigate to other page from root not-found page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/error-boundary-navigation/override-node-env.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - not found navigation - with overridden node env should allow navigating to a non-existent page",
"app dir - not found navigation - with overridden node env should allow navigating to a page calling notfound",
"app dir - not found navigation - with overridden node env should allow navigation back to route that was initially not-found",
"app dir - not found navigation - with overridden node env should allow navigation on error",
"app dir - not found navigation - with overridden node env should allow navigation on not-found",
"app dir - not found navigation - with overridden node env should allow navigation to other routes on route that was initially not-found",
"app dir - not found navigation - with overridden node env should be able to navigate to other page from root not-found page",
"app dir - not found navigation should allow navigating to a non-existent page",
"app dir - not found navigation should allow navigating to a page calling notfound",
"app dir - not found navigation should allow navigation back to route that was initially not-found",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"app dir - not found navigation should allow navigation on error",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - not found navigation should allow navigation on not-found",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"app dir - not found navigation should allow navigation to other routes on route that was initially not-found",
"app dir - not found navigation should be able to navigate to other page from root not-found page"
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"test/e2e/app-dir/externals/externals.test.ts": {
enable e2e tests with turbopack (#57432) Closes WEB-1862 --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-10-25 19:46:31 +02:00
"passed": [],
"failed": [
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"externals-app should have externals for those in config.experimental.serverComponentsExternalPackages",
"externals-app uses externals for predefined list in server-external-packages.json"
],
"pending": [],
"flakey": [],
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"test/e2e/app-dir/front-redirect-issue/front-redirect-issue.test.ts": {
"passed": ["app dir - front redirect issue should redirect"],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/global-error/basic/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"app dir - global error should catch metadata error in error boundary if presented",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - global error should catch metadata error in global-error if no error boundary is presented",
"app dir - global error should render global error for error in client components",
"app dir - global error should render global error for error in server components",
"app dir - global error should trigger error component when an error happens during rendering"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"test/e2e/app-dir/global-error/catch-all/index.test.ts": {
"passed": [
"app dir - global error - with catch-all route should render catch-all route correctly"
],
"failed": [
"app dir - global error - with catch-all route should render 404 page correctly"
],
"pending": [],
"flakey": [],
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"test/e2e/app-dir/global-error/layout-error/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"app dir - global error - layout error should render global error for error in server components"
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/headers-static-bailout/headers-static-bailout.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": ["headers-static-bailout should skip"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/hello-world/hello-world.test.ts": {
"passed": [
"hello-world should work using browser",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"hello-world should work using cheerio",
"hello-world should work with fetch",
"hello-world should work with html"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/hooks/hooks.test.ts": {
"passed": [
"app dir - hooks from pages should have the correct hooks",
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"app dir - hooks useDraftMode should generate rand when draft mode enabled",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - hooks useDraftMode should use initial rand when draft mode be disabled",
"app dir - hooks usePathname should have the canonical url pathname on rewrite",
"app dir - hooks usePathname should have the correct pathname",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"app dir - hooks useRouter should allow access to the router",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - hooks useSearchParams should have the canonical url search params on rewrite",
"app dir - hooks useSearchParams should have the correct search params",
"app dir - hooks useSelectedLayoutSegment should have the correct layout segment at /hooks/use-selected-layout-segment/first",
"app dir - hooks useSelectedLayoutSegment should have the correct layout segment at /hooks/use-selected-layout-segment/first/slug1",
"app dir - hooks useSelectedLayoutSegment should have the correct layout segment at /hooks/use-selected-layout-segment/first/slug2/second/a/b",
"app dir - hooks useSelectedLayoutSegment should return null in pages",
"app dir - hooks useSelectedLayoutSegments should have the correct layout segments at /hooks/use-selected-layout-segment/first",
"app dir - hooks useSelectedLayoutSegments should have the correct layout segments at /hooks/use-selected-layout-segment/first/slug1",
"app dir - hooks useSelectedLayoutSegments should have the correct layout segments at /hooks/use-selected-layout-segment/first/slug2/second",
"app dir - hooks useSelectedLayoutSegments should have the correct layout segments at /hooks/use-selected-layout-segment/first/slug2/second/a/b",
"app dir - hooks useSelectedLayoutSegments should have the correct layout segments at /hooks/use-selected-layout-segment/rewritten",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app dir - hooks useSelectedLayoutSegments should have the correct layout segments at /hooks/use-selected-layout-segment/rewritten-middleware",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - hooks useSelectedLayoutSegments should return an empty array in pages"
],
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"test/e2e/app-dir/i18n-hybrid/i18n-hybrid.test.js": {
"passed": [
"i18n-hybrid does not resolve /en-CA/blog/first-post",
"i18n-hybrid does not resolve /en-US/blog/first-post",
"i18n-hybrid does not resolve /fr-CA/blog/first-post",
"i18n-hybrid does not resolve /fr-FR/blog/first-post",
"i18n-hybrid does resolve /about",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n-hybrid does resolve /blog/first-post",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"i18n-hybrid does resolve /en-CA/about",
"i18n-hybrid does resolve /en-US/about",
"i18n-hybrid does resolve /fr-CA/about",
"i18n-hybrid does resolve /fr-FR/about"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/import/import.test.ts": {
"passed": [
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - imports we can import all components from .js",
"app dir - imports we can import all components from .jsx",
"app dir - imports we can import all components from .ts",
"app dir - imports we can import all components from .tsx"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"test/e2e/app-dir/interception-dynamic-segment/interception-dynamic-segment.test.ts": {
"passed": [
"interception-dynamic-segment should work when interception route is paired with a dynamic segment"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/interception-middleware-rewrite/interception-middleware-rewrite.test.ts": {
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"passed": [
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"interception-middleware-rewrite should continue to show the intercepted page when revisiting it",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"interception-middleware-rewrite should continue to work after using browser back button and following another intercepting route",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"interception-middleware-rewrite should support intercepting routes with a middleware rewrite"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"test/e2e/app-dir/interception-route-groups/interception-route-groups.test.ts": {
"passed": [
"interception route groups (no default) should use the default fallback (a 404) if there is no custom default page"
],
"failed": [
"interception route groups (with default) should render the root default when a route group doesn't have a default",
"interception route groups (with default) should work when nested a level deeper"
],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/e2e/app-dir/interception-route-prefetch-cache/interception-route-prefetch-cache.test.ts": {
"passed": [
"interception-route-prefetch-cache should render the correct interception when two distinct layouts share the same path structure"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/e2e/app-dir/interception-routes-root-catchall/interception-routes-root-catchall.test.ts": {
"passed": [
"interception-routes-root-catchall should handle non-intercepted catch-all pages",
"interception-routes-root-catchall should support having a root catch-all and a catch-all in a parallel route group"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"test/e2e/app-dir/interoperability-with-pages/navigation.test.ts": {
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"passed": [
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"navigation between pages and app dir It should be able to navigate app -> pages",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"navigation between pages and app dir It should be able to navigate app -> pages and go back and forward",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"navigation between pages and app dir It should be able to navigate pages -> app",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"navigation between pages and app dir It should be able to navigate pages -> app and go back an forward"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/layout-params/layout-params.test.ts": {
"passed": [
"app dir - layout params basic params check layout renders just it's params",
"app dir - layout params basic params check layout without params get no params",
"app dir - layout params basic params check topmost layout renders all params",
"app dir - layout params catchall params should give catchall params just to last layout",
"app dir - layout params catchall params should give empty optional catchall params won't give params to any layout",
"app dir - layout params catchall params should give optional catchall params just to last layout"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"test/e2e/app-dir/logging/fetch-logging.test.ts": {
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"passed": [
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"app-dir - logging with default logging should not contain metadata internal segments for dynamic metadata routes",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"app-dir - logging with default logging should not contain trailing word page for app router routes",
Fix app-dir - logging test in Turbopack (#59261) Ensures the app-dir - logging tests pass with Turbopack enabled. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> Closes NEXT-1795
2023-12-05 13:47:32 +01:00
"app-dir - logging with default logging should not log fetch requests at all",
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"app-dir - logging with fetches default logging should log 'skip' cache status with a reason when cache: 'no-cache' is used",
"app-dir - logging with fetches default logging should log 'skip' cache status with a reason when revalidate: 0 is used",
"app-dir - logging with fetches default logging should log 'skip' cache status with a reason when the browser indicates caching should be ignored",
"app-dir - logging with fetches default logging should log requests with correct indentation",
"app-dir - logging with fetches default logging should not contain metadata internal segments for dynamic metadata routes",
"app-dir - logging with fetches default logging should not contain trailing word page for app router routes",
"app-dir - logging with fetches default logging should only log requests in dev mode",
"app-dir - logging with fetches verbose logging should log 'skip' cache status with a reason when cache: 'no-cache' is used",
"app-dir - logging with fetches verbose logging should log 'skip' cache status with a reason when revalidate: 0 is used",
"app-dir - logging with fetches verbose logging should log 'skip' cache status with a reason when the browser indicates caching should be ignored",
"app-dir - logging with fetches verbose logging should log requests with correct indentation",
"app-dir - logging with fetches verbose logging should not contain metadata internal segments for dynamic metadata routes",
"app-dir - logging with fetches verbose logging should not contain trailing word page for app router routes",
"app-dir - logging with fetches verbose logging should only log requests in dev mode",
Fix app-dir - logging test in Turbopack (#59261) Ensures the app-dir - logging tests pass with Turbopack enabled. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> Closes NEXT-1795
2023-12-05 13:47:32 +01:00
"app-dir - logging with verbose logging for edge runtime should not contain metadata internal segments for dynamic metadata routes",
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"app-dir - logging with verbose logging for edge runtime should not contain trailing word page for app router routes",
"app-dir - logging with verbose logging for edge runtime should not log fetch requests at all"
Fix app-dir - logging test in Turbopack (#59261) Ensures the app-dir - logging tests pass with Turbopack enabled. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> Closes NEXT-1795
2023-12-05 13:47:32 +01:00
],
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"failed": [],
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"pending": [],
"flakey": [],
"runtimeError": false
},
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"test/e2e/app-dir/logging/fetch-warning.test.ts": {
"passed": [
"app-dir - fetch warnings should log when request input is a Request instance",
"app-dir - fetch warnings should log when request input is a string",
"app-dir - fetch warnings should not log when overriding cache within the Request object"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"test/e2e/app-dir/mdx/mdx.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"mdx with-mdx-rs app directory should allow importing client components",
"mdx with-mdx-rs app directory should allow overriding components",
"mdx with-mdx-rs app directory should work in initial html",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"mdx with-mdx-rs app directory should work in initial html with mdx import",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"mdx with-mdx-rs app directory should work using browser",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"mdx with-mdx-rs app directory should work using browser with mdx import",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"mdx with-mdx-rs pages directory should allow overriding components",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"mdx with-mdx-rs pages directory should work in initial html",
"mdx with-mdx-rs pages directory should work in initial html with mdx import",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"mdx with-mdx-rs pages directory should work using browser",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"mdx with-mdx-rs pages directory should work using browser with mdx import"
],
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/e2e/app-dir/metadata-dynamic-routes/index.test.ts": {
"passed": [
"app dir - metadata dynamic routes icon image routes should render apple icon with dynamic routes",
"app dir - metadata dynamic routes icon image routes should render icon with dynamic routes",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app dir - metadata dynamic routes should error when id is missing in generateImageMetadata",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"app dir - metadata dynamic routes should error when id is missing in generateSitemaps",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"app dir - metadata dynamic routes should generate unique path for image routes under group routes",
enable e2e tests with turbopack (#57432) Closes WEB-1862 --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-10-25 19:46:31 +02:00
"app dir - metadata dynamic routes should inject dynamic metadata properly to head",
"app dir - metadata dynamic routes should pick configured metadataBase instead of deployment url for canonical url",
"app dir - metadata dynamic routes should use localhost for local prod and fallback to deployment url when metadataBase is falsy",
"app dir - metadata dynamic routes social image routes should fill params into dynamic routes url of metadata images",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"app dir - metadata dynamic routes social image routes should fill params into routes groups url of static images",
fix(next-core): fix determining dynamic route (#57435) ### What Fixes how to determine if given route is dynamic to match next-dev does: https://github.com/vercel/next.js/blob/462b8585b61b83fa079f40e2d8432cc643bf0713/packages/next/src/lib/metadata/get-metadata-route.ts#L79 We were passing calculated route instead to check if it's dynamic, so `/sitemap` always considered as static since calculated route is `/sitemap.xml`. Closes WEB-1864 Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-10-26 01:29:39 +02:00
"app dir - metadata dynamic routes social image routes should handle manifest.[ext] dynamic routes",
"app dir - metadata dynamic routes social image routes should render og image with opengraph-image dynamic routes",
enable e2e tests with turbopack (#57432) Closes WEB-1862 --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-10-25 19:46:31 +02:00
"app dir - metadata dynamic routes social image routes should render og image with twitter-image dynamic routes",
"app dir - metadata dynamic routes social image routes should support generate multi images with generateImageMetadata",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - metadata dynamic routes social image routes should support generate multi sitemaps with generateSitemaps",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"app dir - metadata dynamic routes social image routes should support params as argument in dynamic routes",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"app dir - metadata dynamic routes text routes should handle robots.[ext] dynamic routes",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - metadata dynamic routes text routes should handle sitemap.[ext] dynamic routes",
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"app dir - metadata dynamic routes text routes should not throw if client components are imported but not used"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
fix(next-core): fix determining dynamic route (#57435) ### What Fixes how to determine if given route is dynamic to match next-dev does: https://github.com/vercel/next.js/blob/462b8585b61b83fa079f40e2d8432cc643bf0713/packages/next/src/lib/metadata/get-metadata-route.ts#L79 We were passing calculated route instead to check if it's dynamic, so `/sitemap` always considered as static since calculated route is `/sitemap.xml`. Closes WEB-1864 Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-10-26 01:29:39 +02:00
"failed": [
Update rust-toolchain to 2023-11-16 (#58558) This updates the rust toolchain to 2023-11-16 and: - Removes now-unnecessary `#![feature(async_fn_in_trait)]` - Applies auto-fixable lint fixes - Uses `Cargo.toml` new `lint` section instead of command line rustc flags Test Plan: Tested with updated turbo in a create-next-app Closes PACK-1979 Co-authored-by: OJ Kwon <1210596+kwonoj@users.noreply.github.com>
2023-11-18 01:29:50 +01:00
"app dir - metadata dynamic routes should error if the default export of dynamic image is missing",
"app dir - metadata dynamic routes social image routes should handle custom fonts in both edge and nodejs runtime"
fix(next-core): fix determining dynamic route (#57435) ### What Fixes how to determine if given route is dynamic to match next-dev does: https://github.com/vercel/next.js/blob/462b8585b61b83fa079f40e2d8432cc643bf0713/packages/next/src/lib/metadata/get-metadata-route.ts#L79 We were passing calculated route instead to check if it's dynamic, so `/sitemap` always considered as static since calculated route is `/sitemap.xml`. Closes WEB-1864 Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-10-26 01:29:39 +02:00
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/metadata-edge/index.test.ts": {
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - Metadata API on the Edge runtime should render OpenGraph image meta tag correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/metadata-missing-metadata-base/index.test.ts": {
"passed": [
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"app dir - metadata missing metadataBase should fallback to localhost if metadataBase is missing for absolute urls resolving",
"app dir - metadata missing metadataBase should warn for unsupported metadata properties"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/metadata-suspense/index.test.ts": {
"passed": [
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"app dir - metadata dynamic routes suspense should render metadata in head even root layout is wrapped with Suspense"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/metadata/metadata.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - metadata basic should apply metadata when navigating client-side",
"app dir - metadata basic should handle metadataBase for urls resolved as only URL type",
"app dir - metadata basic should relative canonical url",
"app dir - metadata basic should support alternate tags",
"app dir - metadata basic should support appLinks tags",
"app dir - metadata basic should support apple related tags `itunes` and `appWebApp`",
"app dir - metadata basic should support generateMetadata export",
"app dir - metadata basic should support other basic tags",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - metadata basic should support other basic tags (edge)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - metadata basic should support robots tags",
"app dir - metadata basic should support stashed title in one layer of page and layout",
"app dir - metadata basic should support stashed title in two layers of page and layout",
"app dir - metadata basic should support title and description",
"app dir - metadata basic should support title template",
"app dir - metadata basic should support verification tags",
"app dir - metadata basic should use parent layout title when no title is defined in page",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"app dir - metadata file based icons should not render if image file is not specified",
"app dir - metadata file based icons should render icon and apple touch icon meta if their images are specified",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - metadata icons should merge icons from layout if no static icons files are specified",
"app dir - metadata icons should not hoist meta[itemProp] to head",
"app dir - metadata icons should support basic complex descriptor icons field",
"app dir - metadata icons should support basic object icons field",
"app dir - metadata icons should support basic string icons field",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - metadata icons should support root level of favicon.ico",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"app dir - metadata navigation should render root not-found with default metadata",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - metadata navigation should support notFound in generateMetadata",
"app dir - metadata navigation should support redirect in generateMetadata",
"app dir - metadata opengraph should override file based images when opengraph-image and twitter-image specify images property",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - metadata opengraph should pick up opengraph-image and twitter-image as static metadata files",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - metadata opengraph should support opengraph tags",
"app dir - metadata opengraph should support opengraph with article type",
"app dir - metadata should not effect metadata images convention like files under pages directory",
"app dir - metadata static routes should have /favicon.ico as route",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"app dir - metadata static routes should support root dir robots.txt",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - metadata static routes should support sitemap.xml under every routes",
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"app dir - metadata static routes should support static manifest.webmanifest"
],
"failed": [],
"pending": [],
"flakey": [
"app dir - metadata file based icons should handle updates to the file icon name and order",
"app dir - metadata react cache should have same title and page value on initial load",
"app dir - metadata react cache should have same title and page value when navigating",
"app dir - metadata static routes should have icons as route",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - metadata twitter should render twitter card summary when image is not present",
"app dir - metadata twitter should support default twitter app card",
"app dir - metadata twitter should support default twitter player card",
enable e2e tests with turbopack (#57432) Closes WEB-1862 --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-10-25 19:46:31 +02:00
"app dir - metadata twitter should support twitter card summary_large_image when image present",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"app dir - metadata viewport should support dynamic viewport export"
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"test/e2e/app-dir/mjs-as-extension/mjs-as-extension.test.ts": {
"passed": ["mjs as extension should render the page correctly"],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/e2e/app-dir/modularizeimports/modularizeimports.test.ts": {
"passed": [
"modularizeImports should work",
"modularizeImports should work with MDX"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/navigation/navigation.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - navigation SEO should contain default meta tags in error page",
"app dir - navigation SEO should emit noindex meta tag for not found page when streaming",
"app dir - navigation SEO should emit refresh meta tag (permanent) for redirect page when streaming",
"app dir - navigation SEO should emit refresh meta tag for redirect page when streaming",
"app dir - navigation SEO should not log 404 errors in ipc server",
"app dir - navigation bots should block rendering for bots and return 404 status",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app dir - navigation external push should push external url without affecting hooks",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - navigation hash should not scroll to hash when scroll={false} is set",
"app dir - navigation hash should scroll to the specified hash",
"app dir - navigation hash-link-back-to-same-page should scroll to the specified hash",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app dir - navigation hash-with-scroll-offset should scroll to the specified hash",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"app dir - navigation navigation between pages and app should not contain _rsc query while navigating from app to pages",
"app dir - navigation navigation between pages and app should not contain _rsc query while navigating from pages to app",
"app dir - navigation navigation between pages and app should not omit the hash while navigating from app to pages",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - navigation navigations when attaching a Proxy to `window.Promise` should navigate without issue",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"app dir - navigation nested navigation should load chunks correctly without double encoding of url",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - navigation nested navigation should navigate to nested pages",
"app dir - navigation not-found should trigger not-found client-side",
"app dir - navigation not-found should trigger not-found in a client component",
"app dir - navigation not-found should trigger not-found in a server component",
"app dir - navigation not-found should trigger not-found while streaming",
"app dir - navigation query string should handle unicode search params",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"app dir - navigation query string should not reset shallow url updates on prefetch",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app dir - navigation query string should set query correctly",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"app dir - navigation query string useParams identity between renders should be stable in app",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - navigation redirect components should redirect client-side",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app dir - navigation redirect components should redirect in a client component",
"app dir - navigation redirect components should redirect in a server component",
"app dir - navigation redirect components should redirect to external url",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - navigation redirect components should redirect to external url, initiating only once",
"app dir - navigation redirect middleware redirects should redirect from middleware",
"app dir - navigation redirect middleware redirects should redirect from middleware with link navigation",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app dir - navigation redirect next.config.js redirects should redirect from next.config.js",
"app dir - navigation redirect next.config.js redirects should redirect from next.config.js with link navigation",
"app dir - navigation redirect status code should respond with 307 status code in client component",
"app dir - navigation redirect status code should respond with 307 status code in server component",
"app dir - navigation redirect status code should respond with 308 status code if permanent flag is set",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - navigation relative hashes and queries should work with a hash-only `router.push(...)`",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app dir - navigation relative hashes and queries should work with a hash-only href",
"app dir - navigation relative hashes and queries should work with a query-only href",
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"app dir - navigation relative hashes and queries should work with both relative hashes and queries",
"app dir - navigation scroll restoration should restore original scroll position when navigating back"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#60371) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-08 10:23:29 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
chore: skip flaky turbopack navigation test (#60431) Tracking issue for fixing the test: https://linear.app/vercel/issue/PACK-2203/fix-flaky-navigation-e2e-test Closes PACK-2204
2024-01-09 15:25:08 +01:00
"flakey": [
"app dir - navigation query string useParams identity between renders should be stable in pages"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/next-config/index.test.ts": {
"passed": [
"app dir - next config should support importing webpack in next.config"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/next-font/next-font.test.ts": {
"passed": [],
"failed": [
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"app dir - next/font app app dir - next-font Dev errors should recover on font loader error",
"app dir - next/font app app dir - next-font computed styles should have correct styles at /",
"app dir - next/font app app dir - next-font computed styles should have correct styles at /client",
"app dir - next/font app app dir - next-font import values should have correct values at /",
"app dir - next/font app app dir - next-font import values should have correct values at /client",
"app dir - next/font app app dir - next-font import values should transform code in node_modules",
"app dir - next/font app app dir - next-font navigation should not have duplicate preload tags on navigation",
"app dir - next/font app-old app dir - next-font Dev errors should recover on font loader error",
"app dir - next/font app-old app dir - next-font computed styles should have correct styles at /",
"app dir - next/font app-old app dir - next-font computed styles should have correct styles at /client",
"app dir - next/font app-old app dir - next-font import values should have correct values at /",
"app dir - next/font app-old app dir - next-font import values should have correct values at /client",
"app dir - next/font app-old app dir - next-font import values should transform code in node_modules",
"app dir - next/font app-old app dir - next-font navigation should not have duplicate preload tags on navigation"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/next-image/next-image-https.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - next-image (with https) only runs on CI as it requires administrator privileges"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"test/e2e/app-dir/next-image/next-image-proxy.test.ts": {
"passed": [],
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"failed": [
"next-image-proxy loads images without any errors",
"next-image-proxy should work with connection upgrade by removing it via filterReqHeaders()"
],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"pending": [],
"flakey": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"runtimeError": false
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/next-image/next-image.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - next-image browser content should render images nested under page dir on /nested route",
"app dir - next-image browser content should render images on / route",
"app dir - next-image browser content should render images on /client route",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"app dir - next-image image content should render images nested under page dir on /nested route",
"app dir - next-image image content should render images on /client route",
"app dir - next-image image content should render legacy images under /legacy route",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - next-image ssr content should render images nested under page dir on /nested route",
"app dir - next-image ssr content should render images on / route",
"app dir - next-image ssr content should render images on /client route"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
test(next-image): adjust assertion compatible to turbopack (#57350) ### What Updating test assertions to work with turbopack as well. Closes WEB-1843
2023-10-25 00:25:57 +02:00
"failed": [
"app dir - next-image image content should render images on / route",
"app dir - next-image image content should render legacy images in edge runtime on /legacy-edge-runtime route"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/not-found-default/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - not found with default 404 page should be able to navigate to page calling not-found",
"app dir - not found with default 404 page should be able to navigate to page with calling not-found in metadata",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app dir - not found with default 404 page should error on client notFound from root layout in browser",
"app dir - not found with default 404 page should error on server notFound from root layout on server-side"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - not found with default 404 page should render default 404 with root layout for non-existent page",
"app dir - not found with default 404 page should render default not found for group routes if not found is not defined"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/not-found/basic/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - not-found - basic with default runtime should escalate notFound to parent layout if no not-found boundary present in current layer",
"app dir - not-found - basic with default runtime should match dynamic route not-found boundary correctly",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"app dir - not-found - basic with default runtime should not reload the page",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"app dir - not-found - basic with default runtime should render the 404 page when the file is removed, and restore the page when re-added",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - not-found - basic with default runtime should use the not-found page for non-matching routes",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - not-found - basic with runtime = edge should escalate notFound to parent layout if no not-found boundary present in current layer",
"app dir - not-found - basic with runtime = edge should match dynamic route not-found boundary correctly",
"app dir - not-found - basic with runtime = edge should not reload the page",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"app dir - not-found - basic with runtime = edge should render the 404 page when the file is removed, and restore the page when re-added",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - not-found - basic with runtime = edge should use the not-found page for non-matching routes"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/not-found/conflict-route/index.test.ts": {
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"passed": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - not-found - conflict route with default runtime should use the not-found page for non-matching routes",
"app dir - not-found - conflict route with runtime = edge should use the not-found page for non-matching routes"
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
"app dir - not-found - conflict route with default runtime should allow to have a valid /not-found route",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - not-found - conflict route with runtime = edge should allow to have a valid /not-found route"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/not-found/css-precedence/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
"not-found app dir css should load css while navigation between not-found and page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/not-found/group-route-root-not-found/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"app dir - group routes with root not-found should render default 404 with root layout for non-existent page",
"app dir - group routes with root not-found should render root not found for group routes if hit 404"
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/not-found/group-route/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - not-found - group route with default runtime should use the not-found page under group routes",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - not-found - group route with runtime = edge should use the not-found page under group routes"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/pages-to-app-routing/pages-to-app-routing.test.ts": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": ["pages-to-app-routing should work using browser"],
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"test/e2e/app-dir/parallel-route-not-found/parallel-route-not-found.test.ts": {
"passed": [
"parallel-route-not-found should not log any warnings for a regular not found page",
"parallel-route-not-found should render the page & slots if all parallel routes are found"
],
"failed": [
"parallel-route-not-found should handle a layout that attempts to render a missing parallel route",
"parallel-route-not-found should handle multiple missing parallel routes"
],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/parallel-routes-and-interception/parallel-routes-and-interception.test.ts": {
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"passed": [
"parallel-routes-and-interception parallel routes should display all parallel route params with useParams",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"parallel-routes-and-interception parallel routes should gracefully handle when two page segments match the `children` parallel slot",
feat(turbopack): add support for parallel routes and route interception (#57450) ### What? We have to walk the directory tree recursively for every page (instead of once) to get the correct loaderTree. With this PR we walk the directory tree and for every `page.(js,jsx,ts,tsx)` (entrypoint) we find we walk it again to get the loader tree for that page Closes WEB-1868 Closes WEB-1609
2023-10-26 03:50:00 +02:00
"parallel-routes-and-interception parallel routes should match parallel routes",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"parallel-routes-and-interception parallel routes should match parallel routes in route groups",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"parallel-routes-and-interception parallel routes should navigate with a link with prefetch=false",
"parallel-routes-and-interception parallel routes should only scroll to the parallel route that was navigated to",
feat(turbopack): add support for parallel routes and route interception (#57450) ### What? We have to walk the directory tree recursively for every page (instead of once) to get the correct loaderTree. With this PR we walk the directory tree and for every `page.(js,jsx,ts,tsx)` (entrypoint) we find we walk it again to get the loader tree for that page Closes WEB-1868 Closes WEB-1609
2023-10-26 03:50:00 +02:00
"parallel-routes-and-interception parallel routes should render nested parallel routes",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"parallel-routes-and-interception parallel routes should support layout files in parallel routes",
"parallel-routes-and-interception parallel routes should support nested parallel routes",
"parallel-routes-and-interception parallel routes should support parallel route tab bars",
"parallel-routes-and-interception parallel routes should support parallel routes with no page component",
"parallel-routes-and-interception parallel routes should throw a 404 when no matching parallel route is found",
feat(turbopack): add support for parallel routes and route interception (#57450) ### What? We have to walk the directory tree recursively for every page (instead of once) to get the correct loaderTree. With this PR we walk the directory tree and for every `page.(js,jsx,ts,tsx)` (entrypoint) we find we walk it again to get the loader tree for that page Closes WEB-1868 Closes WEB-1609
2023-10-26 03:50:00 +02:00
"parallel-routes-and-interception route intercepting should re-render the layout on the server when it had a default child route",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"parallel-routes-and-interception route intercepting should render an intercepted route at the top level from a nested path",
"parallel-routes-and-interception route intercepting should render an intercepted route from a slot",
feat(turbopack): add support for parallel routes and route interception (#57450) ### What? We have to walk the directory tree recursively for every page (instead of once) to get the correct loaderTree. With this PR we walk the directory tree and for every `page.(js,jsx,ts,tsx)` (entrypoint) we find we walk it again to get the loader tree for that page Closes WEB-1868 Closes WEB-1609
2023-10-26 03:50:00 +02:00
"parallel-routes-and-interception route intercepting should render intercepted route",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"parallel-routes-and-interception route intercepting should render intercepted route from a nested route",
feat(turbopack): add support for parallel routes and route interception (#57450) ### What? We have to walk the directory tree recursively for every page (instead of once) to get the correct loaderTree. With this PR we walk the directory tree and for every `page.(js,jsx,ts,tsx)` (entrypoint) we find we walk it again to get the loader tree for that page Closes WEB-1868 Closes WEB-1609
2023-10-26 03:50:00 +02:00
"parallel-routes-and-interception route intercepting should render modal when paired with parallel routes",
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"parallel-routes-and-interception route intercepting should support intercepting local dynamic sibling routes",
feat(turbopack): add support for parallel routes and route interception (#57450) ### What? We have to walk the directory tree recursively for every page (instead of once) to get the correct loaderTree. With this PR we walk the directory tree and for every `page.(js,jsx,ts,tsx)` (entrypoint) we find we walk it again to get the loader tree for that page Closes WEB-1868 Closes WEB-1609
2023-10-26 03:50:00 +02:00
"parallel-routes-and-interception route intercepting should support intercepting with beforeFiles rewrites",
"parallel-routes-and-interception route intercepting with dynamic catch-all routes should render intercepted route",
"parallel-routes-and-interception route intercepting with dynamic optional catch-all routes should render intercepted route",
"parallel-routes-and-interception route intercepting with dynamic routes should render intercepted route"
],
"failed": [
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"parallel-routes-and-interception parallel routes should apply the catch-all route to the parallel route if no matching route is found",
"parallel-routes-and-interception parallel routes should match the catch-all routes of the more specific path, if there is more than one catch-all route"
],
"pending": [],
Update Turbopack test manifest (#60371) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-08 10:23:29 +01:00
"flakey": [],
"runtimeError": false
},
"test/e2e/app-dir/parallel-routes-catchall-children-slot/parallel-routes-catchall-children-slot.test.ts": {
"passed": [],
"failed": [
"parallel-routes-catchall-children-slot should match the @children slot for a page before attempting to match the catchall"
],
"pending": [],
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"flakey": [],
"runtimeError": false
},
"test/e2e/app-dir/parallel-routes-catchall-default/parallel-routes-catchall-default.test.ts": {
"passed": [
"parallel-routes-catchall-default should match default paths before catch-all"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/e2e/app-dir/parallel-routes-catchall-groups/parallel-routes-catchall-groups.test.ts": {
"passed": [
"parallel-routes-catchall-groups should work without throwing any errors about conflicting paths"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/e2e/app-dir/parallel-routes-catchall/parallel-routes-catchall.test.ts": {
"passed": [],
"failed": [
"parallel-routes-catchall should match both the catch-all page & slot",
"parallel-routes-catchall should match correctly when defining an explicit page & slot",
"parallel-routes-catchall should match correctly when defining an explicit page but no slot",
"parallel-routes-catchall should match correctly when defining an explicit slot but no page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/parallel-routes-not-found/parallel-routes-not-found.test.ts": {
feat(turbopack): add support for parallel routes and route interception (#57450) ### What? We have to walk the directory tree recursively for every page (instead of once) to get the correct loaderTree. With this PR we walk the directory tree and for every `page.(js,jsx,ts,tsx)` (entrypoint) we find we walk it again to get the loader tree for that page Closes WEB-1868 Closes WEB-1609
2023-10-26 03:50:00 +02:00
"passed": [
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"parallel-routes-and-interception should not render the @children slot when the @slot is not found"
],
feat(turbopack): add support for parallel routes and route interception (#57450) ### What? We have to walk the directory tree recursively for every page (instead of once) to get the correct loaderTree. With this PR we walk the directory tree and for every `page.(js,jsx,ts,tsx)` (entrypoint) we find we walk it again to get the loader tree for that page Closes WEB-1868 Closes WEB-1609
2023-10-26 03:50:00 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"test/e2e/app-dir/parallel-routes-revalidation/parallel-routes-revalidation.test.ts": {
"passed": [
"parallel-routes-revalidation should handle a redirect action when called in a slot",
"parallel-routes-revalidation should handle router.refresh() when called in a slot",
"parallel-routes-revalidation should submit the action and revalidate the page data"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"test/e2e/app-dir/params-hooks-compat/index.test.ts": {
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir - params hooks compat should only access path params with useParams",
"app-dir - params hooks compat should only access search params with useSearchParams"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"test/e2e/app-dir/ppr-errors/ppr-errors.test.ts": {
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"passed": [],
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"failed": [],
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"pending": [
"ppr build errors production mode outside of a suspense boundary should fail the build for uncaught errors",
"ppr build errors production mode outside of a suspense boundary when a postpone call was made but missing postpone data should fail the build",
"ppr build errors production mode outside of a suspense boundary when a postpone call was made but missing postpone data should fail the build & surface any errors that were thrown by user code",
"ppr build errors production mode when a postpone call is caught and logged it should should include a message telling why",
"ppr build errors production mode within a suspense boundary should fail the build for uncaught prerender errors",
"ppr build errors production mode within a suspense boundary when a postpone call was made but missing postpone data should fail the build",
"ppr build errors production mode within a suspense boundary when a postpone call was made but missing postpone data should fail the build & surface any errors that were thrown by user code"
],
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"flakey": [],
"runtimeError": false
},
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"test/e2e/app-dir/ppr-full/ppr-full.test.ts": {
"passed": [
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"ppr-full HTML Response for / should allow navigations to and from a pages/ page",
"ppr-full HTML Response for / should cache the static part",
"ppr-full HTML Response for / should have correct headers",
"ppr-full HTML Response for / should resume with dynamic content",
"ppr-full HTML Response for /dynamic/force-dynamic should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /dynamic/force-dynamic should have correct headers",
"ppr-full HTML Response for /dynamic/force-dynamic should resume with dynamic content",
"ppr-full HTML Response for /dynamic/force-dynamic/nested/a should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /dynamic/force-dynamic/nested/a should have correct headers",
"ppr-full HTML Response for /dynamic/force-dynamic/nested/a should resume with dynamic content",
"ppr-full HTML Response for /dynamic/force-dynamic/nested/b should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /dynamic/force-dynamic/nested/b should have correct headers",
"ppr-full HTML Response for /dynamic/force-dynamic/nested/b should resume with dynamic content",
"ppr-full HTML Response for /dynamic/force-dynamic/nested/c should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /dynamic/force-dynamic/nested/c should have correct headers",
"ppr-full HTML Response for /dynamic/force-dynamic/nested/c should resume with dynamic content",
"ppr-full HTML Response for /dynamic/force-static should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /dynamic/force-static should have correct headers",
"ppr-full HTML Response for /dynamic/force-static should not contain dynamic content",
"ppr-full HTML Response for /loading/a should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /loading/a should cache the static part",
"ppr-full HTML Response for /loading/a should have correct headers",
"ppr-full HTML Response for /loading/a should resume with dynamic content",
"ppr-full HTML Response for /loading/b should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /loading/b should cache the static part",
"ppr-full HTML Response for /loading/b should have correct headers",
"ppr-full HTML Response for /loading/b should resume with dynamic content",
"ppr-full HTML Response for /loading/c should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /loading/c should cache the static part",
"ppr-full HTML Response for /loading/c should have correct headers",
"ppr-full HTML Response for /loading/c should resume with dynamic content",
"ppr-full HTML Response for /nested/a should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /nested/a should cache the static part",
"ppr-full HTML Response for /nested/a should have correct headers",
"ppr-full HTML Response for /nested/a should resume with dynamic content",
"ppr-full HTML Response for /nested/b should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /nested/b should cache the static part",
"ppr-full HTML Response for /nested/b should have correct headers",
"ppr-full HTML Response for /nested/b should resume with dynamic content",
"ppr-full HTML Response for /nested/c should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /nested/c should cache the static part",
"ppr-full HTML Response for /nested/c should have correct headers",
"ppr-full HTML Response for /nested/c should resume with dynamic content",
"ppr-full HTML Response for /no-suspense should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /no-suspense should cache the static part",
"ppr-full HTML Response for /no-suspense should have correct headers",
"ppr-full HTML Response for /no-suspense should resume with dynamic content",
"ppr-full HTML Response for /no-suspense/nested/a should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /no-suspense/nested/a should cache the static part",
"ppr-full HTML Response for /no-suspense/nested/a should have correct headers",
"ppr-full HTML Response for /no-suspense/nested/a should resume with dynamic content",
"ppr-full HTML Response for /no-suspense/nested/b should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /no-suspense/nested/b should cache the static part",
"ppr-full HTML Response for /no-suspense/nested/b should have correct headers",
"ppr-full HTML Response for /no-suspense/nested/b should resume with dynamic content",
"ppr-full HTML Response for /no-suspense/nested/c should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /no-suspense/nested/c should cache the static part",
"ppr-full HTML Response for /no-suspense/nested/c should have correct headers",
"ppr-full HTML Response for /no-suspense/nested/c should resume with dynamic content",
"ppr-full HTML Response for /on-demand/a should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /on-demand/a should cache the static part",
"ppr-full HTML Response for /on-demand/a should have correct headers",
"ppr-full HTML Response for /on-demand/a should resume with dynamic content",
"ppr-full HTML Response for /on-demand/b should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /on-demand/b should cache the static part",
"ppr-full HTML Response for /on-demand/b should have correct headers",
"ppr-full HTML Response for /on-demand/b should resume with dynamic content",
"ppr-full HTML Response for /on-demand/c should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /on-demand/c should cache the static part",
"ppr-full HTML Response for /on-demand/c should have correct headers",
"ppr-full HTML Response for /on-demand/c should resume with dynamic content",
"ppr-full HTML Response for /static should allow navigations to and from a pages/ page",
"ppr-full HTML Response for /static should have correct headers",
"ppr-full HTML Response for /static should not contain dynamic content"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/e2e/app-dir/ppr-navigations/ppr-navigations.test.ts": {
"passed": ["ppr-navigations prefetching is disabled in dev"],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"test/e2e/app-dir/ppr/ppr.test.ts": {
"passed": [
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"ppr /no-suspense/node/gsp/[slug] should serve the static & dynamic parts",
"ppr /suspense/node/gsp/[slug] should not have the dynamic part",
"ppr /suspense/node/gsp/[slug] should serve the static part first",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"ppr for /loading/nested/1 should have the dynamic part",
"ppr for /loading/nested/1 should serve the static part",
"ppr for /loading/nested/2 should have the dynamic part",
"ppr for /loading/nested/2 should serve the static part",
"ppr for /loading/nested/3 should have the dynamic part",
"ppr for /loading/nested/3 should serve the static part",
"ppr for /suspense/node should have the dynamic part",
"ppr for /suspense/node should serve the static part",
"ppr for /suspense/node/nested/1 should have the dynamic part",
"ppr for /suspense/node/nested/1 should serve the static part",
"ppr for /suspense/node/nested/2 should have the dynamic part",
"ppr for /suspense/node/nested/2 should serve the static part",
"ppr for /suspense/node/nested/3 should have the dynamic part",
"ppr for /suspense/node/nested/3 should serve the static part",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"ppr search parameters should render the page with the search parameters",
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"ppr should indicate the feature is experimental",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"ppr with suspense for /suspense/edge should eventually render the dynamic part",
"ppr with suspense for /suspense/node should eventually render the dynamic part",
"ppr without suspense for /no-suspense should immediately render the dynamic part"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"test/e2e/app-dir/revalidate-dynamic/revalidate-dynamic.test.ts": {
"passed": [
"app-dir revalidate-dynamic should revalidate the data with /api/revalidate-path",
"app-dir revalidate-dynamic should revalidate the data with /api/revalidate-tag"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/rewrites-redirects/rewrites-redirects.test.ts": {
"passed": [
"redirects and rewrites navigation using button should redirect from middleware correctly",
"redirects and rewrites navigation using button should redirect from next.config.js correctly",
"redirects and rewrites navigation using button should redirect using catchall from next.config.js correctly",
"redirects and rewrites navigation using button should rewrite from middleware correctly",
"redirects and rewrites navigation using button should rewrite from next.config.js correctly",
"redirects and rewrites navigation using link should redirect from middleware correctly",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"redirects and rewrites navigation using link should redirect from next.config.js correctly",
"redirects and rewrites navigation using link should redirect using catchall from next.config.js correctly",
"redirects and rewrites navigation using link should rewrite from middleware correctly",
"redirects and rewrites navigation using link should rewrite from next.config.js correctly"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"test/e2e/app-dir/root-layout-redirect/root-layout-redirect.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": ["root-layout-redirect should work using browser"],
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/root-layout-render-once/index.test.ts": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"app-dir root layout render once should only render root layout once"
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/root-layout/root-layout.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir root layout Should do a mpa navigation when switching root layout should work with basic routes",
"app-dir root layout Should do a mpa navigation when switching root layout should work with dynamic catchall routes",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app-dir root layout Should do a mpa navigation when switching root layout should work with dynamic routes",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"app-dir root layout Should do a mpa navigation when switching root layout should work with parallel routes",
"app-dir root layout Should do a mpa navigation when switching root layout should work with route groups",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir root layout Should do a mpa navigation when switching root layout should work with static routes",
"app-dir root layout should correctly handle navigation between multiple root layouts"
],
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [
"app-dir root layout Missing required tags should error on page load",
"app-dir root layout Missing required tags should error on page load on static generation",
"app-dir root layout Missing required tags should error on page navigation"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/route-page-manifest-bug/route-page-manifest-bug.test.ts": {
"passed": [
"route-page-manifest-bug should work when requesting route handler after page"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/router-autoscroll/router-autoscroll.test.ts": {
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"router autoscrolling on navigation bugs Should apply scroll when loading.js is used",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"router autoscrolling on navigation bugs Should scroll to the top of the layout when the first child is display none",
"router autoscrolling on navigation bugs Should scroll to the top of the layout when the first child is position fixed",
"router autoscrolling on navigation bugs Should scroll to the top of the layout when the first child is position sticky",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"router autoscrolling on navigation horizontal scroll should't scroll horizontally",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"router autoscrolling on navigation router.refresh() should not scroll when called alone",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"router autoscrolling on navigation router.refresh() should not stop router.push() from scrolling",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"router autoscrolling on navigation vertical scroll should not scroll to top of document if page in viewport",
"router autoscrolling on navigation vertical scroll should not scroll when the top of the page is in the viewport",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"router autoscrolling on navigation vertical scroll should scroll down to the navigated page when it's below viewort",
"router autoscrolling on navigation vertical scroll should scroll to top of document if possible while giving focus to page",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"router autoscrolling on navigation vertical scroll should scroll to top of document when navigating between to pages without layout",
"router autoscrolling on navigation vertical scroll should scroll to top of page when scrolling to phe top of the document wouldn't have the page in the viewport"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [
"router autoscrolling on navigation router.refresh() should not scroll the page when we hot reload"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/router-stuck-dynamic-static-segment/router-stuck-dynamic-static-segment.test.ts": {
"passed": [
"router-stuck-dynamic-static-segment should allow navigation between dynamic parameter and static parameter of the same value"
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/e2e/app-dir/rsc-basic/rsc-basic.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
enable e2e tests with turbopack (#57432) Closes WEB-1862 --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-10-25 19:46:31 +02:00
"app dir - rsc basics react@experimental should opt into the react@experimental when enabling ppr",
"app dir - rsc basics react@experimental should opt into the react@experimental when enabling taint",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"app dir - rsc basics should be able to call legacy react-dom/server APIs in client components",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - rsc basics should be able to navigate between rsc routes",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - rsc basics should correctly render component returning null",
"app dir - rsc basics should correctly render component returning undefined",
"app dir - rsc basics should correctly render layout returning null",
"app dir - rsc basics should correctly render layout returning undefined",
"app dir - rsc basics should correctly render page returning null",
"app dir - rsc basics should correctly render page returning undefined",
enable e2e tests with turbopack (#57432) Closes WEB-1862 --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-10-25 19:46:31 +02:00
"app dir - rsc basics should create client reference successfully for all file conventions",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - rsc basics should escape streaming data correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - rsc basics should handle streaming server components correctly",
"app dir - rsc basics should handle various kinds of exports correctly",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - rsc basics should link correctly with next/link without mpa navigation to the page",
"app dir - rsc basics should not apply rsc syntax checks in pages/api",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - rsc basics should not use bundled react for pages with app",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - rsc basics should render built-in 404 page for missing route if pagesDir is not presented",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - rsc basics should render css-in-js suspense boundary correctly",
"app dir - rsc basics should render initial styles of css-in-js in edge SSR correctly",
"app dir - rsc basics should render initial styles of css-in-js in nodejs SSR correctly",
"app dir - rsc basics should render server components correctly",
"app dir - rsc basics should resolve different kinds of components correctly",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - rsc basics should reuse the inline flight response without sending extra requests",
"app dir - rsc basics should stick to the url without trailing /page suffix",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - rsc basics should support multi-level server component imports",
"app dir - rsc basics should support native modules in server component",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - rsc basics should support next/link in server components",
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"app dir - rsc basics should support partial hydration with inlined server data",
"app dir - rsc basics should support streaming for flight response",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app dir - rsc basics should suspense next/image in server components",
"app dir - rsc basics should suspense next/legacy/image in server components",
"app dir - rsc basics should track client components in dynamic imports",
"app dir - rsc basics should use canary react for app"
],
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - rsc basics should support partial hydration with inlined server data in browser",
"app dir - rsc basics should support webpack loader rules"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"runtimeError": false
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"test/e2e/app-dir/search-params-react-key/layout-params.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"app dir - search params keys should keep the React router instance the same when changing the search params"
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/e2e/app-dir/searchparams-static-bailout/searchparams-static-bailout.test.ts": {
"passed": [
"searchparams-static-bailout client component should bailout when using searchParams",
"searchparams-static-bailout client component should bailout when using searchParams is passed to client component",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"searchparams-static-bailout client component should not bailout when not using searchParams",
"searchparams-static-bailout server component should bailout when using searchParams",
"searchparams-static-bailout server component should not bailout when not using searchParams"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/server-actions-relative-redirect/server-actions-relative-redirect.test.ts": {
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"server-actions-relative-redirect should work with absolute redirect",
"server-actions-relative-redirect should work with relative redirect"
],
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"runtimeError": false
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
},
"test/e2e/app-dir/set-cookies/set-cookies.test.ts": {
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"set-cookies for edge runtime for /app should set two set-cookie headers",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"set-cookies for edge runtime for /pages should set two set-cookie headers",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"set-cookies for experimental-edge runtime for /app should set two set-cookie headers",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"set-cookies for experimental-edge runtime for /pages should set two set-cookie headers",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"set-cookies for node runtime for /app should set two set-cookie headers",
"set-cookies for node runtime for /pages should set two set-cookie headers"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/e2e/app-dir/shallow-routing/shallow-routing.test.ts": {
"passed": [
"shallow-routing back and forward client-side navigation should support setting a different pathname reflected on usePathname and then still support navigating back and forward",
"shallow-routing back and forward mpa navigation should support setting data and then still support navigating back and forward",
"shallow-routing pushState should support setting a different pathname reflected on usePathname",
"shallow-routing pushState should support setting a different searchParam reflected on useSearchParams",
"shallow-routing pushState should support setting a different url using a string",
"shallow-routing pushState should support setting data",
"shallow-routing pushState should work when given a null state value",
"shallow-routing replaceState should support setting a different pathname reflected on usePathname",
"shallow-routing replaceState should support setting a different searchParam reflected on useSearchParams",
"shallow-routing replaceState should support setting a different url using a string",
"shallow-routing replaceState should support setting data",
"shallow-routing replaceState should work when given a null state value",
"shallow-routing replaceState should work when given an undefined state value",
"shallow-routing should work when given an undefined state value"
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/similar-pages-paths/similar-pages-paths.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir similar pages paths should not have conflicts for similar pattern page paths between app and pages"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"test/e2e/app-dir/taint/process-taint.test.ts": {
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"passed": [
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"app dir - taint should error when passing process env to client component"
],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"failed": [],
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"pending": [],
"flakey": [],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"runtimeError": false
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/test-template/{{ toFileName name }}/{{ toFileName name }}.test.ts": {
"passed": [
"{{name}} should work using browser",
"{{name}} should work using cheerio",
"{{name}} should work with fetch",
"{{name}} should work with html"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/e2e/app-dir/third-parties/basic.test.ts": {
"passed": [
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"@next/third-parties basic usage renders GA",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"@next/third-parties basic usage renders GTM",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"@next/third-parties basic usage renders GoogleMapsEmbed",
"@next/third-parties basic usage renders YoutubeEmbed"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/trailingslash/trailingslash.test.ts": {
"passed": [
"app-dir trailingSlash handling should redirect route when clicking link",
"app-dir trailingSlash handling should redirect route when requesting it directly",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"app-dir trailingSlash handling should redirect route when requesting it directly by browser",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app-dir trailingSlash handling should render link with trailing slash"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/underscore-ignore-app-paths/underscore-ignore-app-paths.test.ts": {
"passed": [
"underscore-ignore-app-paths should not serve app path with underscore",
"underscore-ignore-app-paths should serve pages path with underscore"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": ["underscore-ignore-app-paths should serve app path with %5F"],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/use-params/use-params.test.ts": {
"passed": [
"use-params should work for catch all params",
"use-params should work for nested dynamic params",
"use-params should work for nested dynamic params client navigating",
"use-params should work for single dynamic param",
"use-params should work for single dynamic param client navigating"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/use-selected-layout-segment-s/use-selected-layout-segment-s.test.ts": {
"passed": [
"useSelectedLayoutSegment(s) should correctly update when changing catchall segment",
"useSelectedLayoutSegment(s) should correctly update when changing param segment",
"useSelectedLayoutSegment(s) should correctly update when changing static segment",
"useSelectedLayoutSegment(s) should return correct values for root layout",
"useSelectedLayoutSegment(s) should return correct values in layout after last segment",
"useSelectedLayoutSegment(s) should return correct values in layout before catchall segment",
"useSelectedLayoutSegment(s) should return correct values in layout before param segment",
"useSelectedLayoutSegment(s) should return correct values in layout before static segment"
],
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/with-babel/with-babel.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"failed": [],
"pending": ["with babel with babel should support babel in app dir"],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/app-dir/with-exported-function-config/with-exported-function-config.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"with-exported-function-config should have correct values in function config manifest"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"test/e2e/app-dir/x-forwarded-headers/x-forwarded-headers.test.ts": {
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"passed": [
"x-forwarded-headers already assigned should not override existing x-forwarded-* headers",
"x-forwarded-headers host header exists should include x-forwarded-* headers relative to host",
"x-forwarded-headers should include x-forwarded-* headers"
],
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/basepath-trailing-slash.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"basePath + trailingSlash should allow URL query strings on index without refresh",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"basePath + trailingSlash should allow URL query strings without refresh",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"basePath + trailingSlash should correctly replace state when same asPath but different url"
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
"runtimeError": false
},
"test/e2e/basepath.test.ts": {
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"passed": [
"basePath should 404 for public file without basePath",
"basePath should 404 when manually adding basePath with <Link>",
"basePath should add header with basePath by default",
"basePath should add header without basePath when set to false",
"basePath should allow URL query strings on index without refresh",
"basePath should allow URL query strings without refresh",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"basePath should correctly replace state when same asPath but different url",
"basePath should fetch data for getServerSideProps without reloading",
"basePath should fetch data for getStaticProps without reloading",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"basePath should handle 404 urls that start with basePath",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"basePath should handle query/hash correctly during query updating ## $search",
"basePath should handle query/hash correctly during query updating ##? $search",
"basePath should handle query/hash correctly during query updating ##hello $search",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"basePath should handle query/hash correctly during query updating ##hello? $search",
"basePath should handle query/hash correctly during query updating #? $search",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"basePath should handle query/hash correctly during query updating #a ?hello",
"basePath should handle query/hash correctly during query updating #a ?hello=",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"basePath should handle query/hash correctly during query updating #a ?hello=world",
"basePath should handle query/hash correctly during query updating #hello? $search",
"basePath should handle query/hash correctly during query updating #hello?world $search",
"basePath should have basePath field on Router",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"basePath should have correct href for a link",
"basePath should have correct href for a link to /",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"basePath should have correct router paths on first load of /",
"basePath should have correct router paths on first load of /hello",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"basePath should navigate an absolute local url with basePath",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"basePath should navigate an absolute local url without basePath",
"basePath should navigate an absolute url",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"basePath should navigate back correctly to a dynamic route",
"basePath should navigate to /404 correctly client-side",
"basePath should navigate to /_error correctly client-side",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"basePath should navigate to external site and back",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"basePath should navigate to index page with getStaticProps",
"basePath should navigate to the page without refresh",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"basePath should not add header with basePath when set to false",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"basePath should not add header without basePath without disabling",
"basePath should not redirect with basePath when set to false",
"basePath should not redirect without basePath without disabling",
"basePath should not rewrite with basePath when set to false",
"basePath should not rewrite without basePath without disabling",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"basePath should not update URL for a 404",
"basePath should redirect trailing slash correctly",
"basePath should redirect trailing slash on root correctly",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"basePath should redirect with basePath by default",
"basePath should redirect without basePath when set to false",
"basePath should respect basePath in amphtml link rel",
"basePath should rewrite with basePath by default",
"basePath should rewrite without basePath when set to false",
"basePath should serve public file with basePath correctly",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"basePath should show 404 for page not under the /docs prefix",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"basePath should show the hello page under the /docs prefix",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"basePath should show the other-page page under the /docs prefix",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"basePath should update dynamic params after mount correctly",
"basePath should use urls with basepath in router events",
"basePath should use urls with basepath in router events for cancelled routes",
"basePath should use urls with basepath in router events for failed route change",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"basePath should use urls with basepath in router events for hash changes",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"basePath should work with catch-all page",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"basePath should work with hash links",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"basePath should work with nested folder with same name as basePath",
"basePath should work with normal dynamic page"
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"pending": [
"basePath should navigate back to a non-basepath 404 that starts with basepath",
"basePath should navigate to nested index page with getStaticProps"
],
"flakey": [
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"basePath should 404 when manually adding basePath with router.push",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"basePath should 404 when manually adding basePath with router.replace"
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/e2e/browserslist-extends/index.test.ts": {
"passed": ["browserslist-extends should work"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/browserslist/browserslist.test.ts": {
"passed": [],
"failed": ["Browserslist should apply browserslist target"],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/e2e/cancel-request/stream-cancel.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"streaming responses cancel inner stream after disconnect edge app route handler cancels stalled stream",
"streaming responses cancel inner stream after disconnect edge app route handler cancels stream making progress",
"streaming responses cancel inner stream after disconnect edge app route handler cancels stream that never sent data",
"streaming responses cancel inner stream after disconnect edge pages api cancels stalled stream",
"streaming responses cancel inner stream after disconnect edge pages api cancels stream making progress",
"streaming responses cancel inner stream after disconnect edge pages api cancels stream that never sent data",
"streaming responses cancel inner stream after disconnect middleware cancels stalled stream",
"streaming responses cancel inner stream after disconnect middleware cancels stream making progress",
"streaming responses cancel inner stream after disconnect middleware cancels stream that never sent data",
"streaming responses cancel inner stream after disconnect node app route handler cancels stalled stream",
"streaming responses cancel inner stream after disconnect node app route handler cancels stream making progress",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"streaming responses cancel inner stream after disconnect node app route handler cancels stream that never sent data",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"streaming responses cancel inner stream after disconnect node pages api cancels stalled stream",
"streaming responses cancel inner stream after disconnect node pages api cancels stream making progress",
"streaming responses cancel inner stream after disconnect node pages api cancels stream that never sent data"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/children-page/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"children-page with app dir should show the content if you have a page named children",
"children-page with pages dir should show the content if you have a page named children"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/config-promise-export/async-function.test.ts": {
"passed": ["async export should work"],
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/config-promise-export/promise.test.ts": {
"passed": ["promise export should work"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/config-schema-check/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next.config.js schema validating - defaultConfig should validate against defaultConfig"
],
"failed": [
"next.config.js schema validating - invalid config should warn the invalid next config"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"runtimeError": true
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/conflicting-app-page-error/index.test.ts": {
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Conflict between app file and pages file should error again when there is new conflict",
"Conflict between app file and pages file should show error overlay for /",
"Conflict between app file and pages file should show error overlay for /another",
"Conflict between app file and pages file should support hmr with conflicts"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"flakey": [
"Conflict between app file and pages file should not show error overlay for non conflict pages under app or pages dir"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/custom-app-render/custom-app-render.test.ts": {
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"custom-app-render should render /",
"custom-app-render should render /render"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/disable-js-preload/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"disabled JS preloads should not have JS preload links",
"disabled JS preloads should render the page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/dynamic-route-interpolation/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic Route Interpolation should bust data cache",
"Dynamic Route Interpolation should bust data cache with symbol",
"Dynamic Route Interpolation should work",
"Dynamic Route Interpolation should work with brackets",
"Dynamic Route Interpolation should work with brackets in API routes",
"Dynamic Route Interpolation should work with parameter itself",
"Dynamic Route Interpolation should work with parameter itself in API routes"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/edge-api-endpoints-can-receive-body/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Edge API endpoints can receive body reads the body as text",
"Edge API endpoints can receive body reads the body from index"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/edge-async-local-storage/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"edge api can use async local storage cans use a single instance per request",
"edge api can use async local storage cans use multiple instances per request"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/edge-can-read-request-body/index.test.ts": {
"passed": [
"Edge can read request body middleware reads a JSON body",
"Edge can read request body middleware reads a multipart form data",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Edge can read request body middleware reads a text body",
"Edge can read request body middleware reads an URL encoded form data",
"Edge can read request body renders the static page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/edge-can-use-wasm-files/index.test.ts": {
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"edge api endpoints can use wasm files uses the wasm file",
"middleware can use wasm files can be called twice",
"middleware can use wasm files uses the wasm file",
"middleware can use wasm files with the experimental modes on uses the wasm file"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"failed": [
"middleware can use wasm files lists the necessary wasm bindings in the manifest"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/edge-compiler-can-import-blob-assets/index.test.ts": {
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"passed": [],
"failed": [],
"pending": [
Fix mjs import for Turbopack test (#56354) Turbopack currently supports fully-specified `.mjs` imports. Double check with @sokra to verify if this is correct. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-10-03 13:33:04 +02:00
"Edge Compiler can import asset assets allows to assets from node_modules",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"Edge Compiler can import asset assets allows to fetch a remote URL",
"Edge Compiler can import asset assets allows to fetch a remote URL with a path and basename",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Edge Compiler can import asset assets allows to fetch image assets",
Fix mjs import for Turbopack test (#56354) Turbopack currently supports fully-specified `.mjs` imports. Double check with @sokra to verify if this is correct. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-10-03 13:33:04 +02:00
"Edge Compiler can import asset assets allows to fetch text assets",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Edge Compiler can import asset assets extracts all the assets from the bundle"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/edge-compiler-module-exports-preference/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Edge compiler module exports preference favors the browser export"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/edge-configurable-runtime/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Configurable runtime for pages and API routes In dev mode runs with no warning API route on the edge runtime",
"Configurable runtime for src/pages and API routes In dev mode runs with no warning API route on the edge runtime"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Configurable runtime for pages and API routes In dev mode errors about page using edge runtime",
"Configurable runtime for pages and API routes In dev mode warns about API route using experimental-edge runtime",
"Configurable runtime for pages and API routes In dev mode warns about page using edge runtime",
"Configurable runtime for src/pages and API routes In dev mode errors about page using edge runtime",
"Configurable runtime for src/pages and API routes In dev mode warns about API route using experimental-edge runtime",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Configurable runtime for src/pages and API routes In dev mode warns about page using edge runtime"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/edge-pages-support/edge-document.test.ts": {
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"edge render - custom _document with edge runtime should render page properly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/edge-pages-support/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"edge-render-getserversideprops should have correct query for pages/api",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"edge-render-getserversideprops should have correct query for pages/api dynamic",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"edge-render-getserversideprops should have correct query/params on /[id]",
"edge-render-getserversideprops should have correct query/params on dynamic rewrite",
"edge-render-getserversideprops should have correct query/params on index",
"edge-render-getserversideprops should have correct query/params on rewrite",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"edge-render-getserversideprops should respond to _next/data for [id] correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"edge-render-getserversideprops should respond to _next/data for index correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"test/e2e/edge-runtime-pages-api-route/edge-runtime-pages-api-route.test.ts": {
"passed": [
"Edge runtime pages-api route should work edge runtime",
"Edge runtime pages-api route should work with node runtime"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/edge-runtime-uses-edge-light-import-specifier-for-packages/edge-runtime-uses-edge-light-import-specifier-for-packages.test.ts": {
"passed": [],
"failed": [
"edge-runtime uses edge-light import specifier for packages app-dir imports the correct module",
"edge-runtime uses edge-light import specifier for packages pages import the correct module",
"edge-runtime uses edge-light import specifier for packages pages/api endpoints import the correct module"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/favicon-short-circuit/favicon-short-circuit.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"favicon-short-circuit should short circuit the favicon in development"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/fetch-failures-have-good-stack-traces-in-edge-runtime/fetch-failures-have-good-stack-traces-in-edge-runtime.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"fetch failures have good stack traces in edge runtime when awaiting `fetch` using an unknown domain, stack traces are preserved",
"fetch failures have good stack traces in edge runtime when returning `fetch` using an unknown domain, stack traces are preserved"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/getserversideprops/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"getServerSideProps should SSR getServerSideProps page correctly",
"getServerSideProps should SSR normal page correctly",
"getServerSideProps should allow POST request for getServerSideProps page",
"getServerSideProps should always call getServerSideProps without caching",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"getServerSideProps should dedupe server data requests",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"getServerSideProps should handle throw ENOENT correctly",
"getServerSideProps should have correct req.url and query for direct visit",
"getServerSideProps should have correct req.url and query for direct visit dynamic page",
"getServerSideProps should have correct req.url and query for direct visit dynamic page rewrite direct",
"getServerSideProps should have correct req.url and query for direct visit dynamic page rewrite direct with internal query",
"getServerSideProps should have correct req.url and query for direct visit dynamic page rewrite param",
"getServerSideProps should have correct req.url and query for direct visit dynamic page with query",
"getServerSideProps should have gssp in __NEXT_DATA__",
"getServerSideProps should have original req.url for /_next/data request",
"getServerSideProps should have original req.url for /_next/data request dynamic page",
"getServerSideProps should have original req.url for /_next/data request dynamic page with query",
"getServerSideProps should have original req.url for /_next/data request with query",
"getServerSideProps should load a fast refresh page",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"getServerSideProps should navigate between pages successfully",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"getServerSideProps should navigate to a normal page and back",
"getServerSideProps should not have gssp in __NEXT_DATA__ for non-GSSP page",
"getServerSideProps should not re-call getServerSideProps when updating query",
"getServerSideProps should not show warning from url prop being returned",
"getServerSideProps should only warn for accessing res if not streaming",
"getServerSideProps should parse query values on mount correctly",
"getServerSideProps should pass query for data request",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"getServerSideProps should pass query for data request on navigation",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"getServerSideProps should provide correct query value for dynamic page",
"getServerSideProps should reload page on failed data request",
"getServerSideProps should render 404 correctly when notFound is returned (dynamic)",
"getServerSideProps should render 404 correctly when notFound is returned (non-dynamic)",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"getServerSideProps should render 404 correctly when notFound is returned client-transition (dynamic)",
"getServerSideProps should render 404 correctly when notFound is returned client-transition (non-dynamic)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"getServerSideProps should render correctly when notFound is false (dynamic)",
"getServerSideProps should render correctly when notFound is false (non-dynamic)",
"getServerSideProps should return data correctly",
"getServerSideProps should return data correctly for dynamic page",
"getServerSideProps should return data correctly when props is a promise",
"getServerSideProps should show error for accessing res after gssp returns",
"getServerSideProps should show error for accessing res through props promise after gssp returns",
"getServerSideProps should show error for extra keys returned from getServerSideProps",
"getServerSideProps should show error for invalid JSON returned from getServerSideProps",
"getServerSideProps should show error for invalid JSON returned from getStaticProps on CST",
"getServerSideProps should supply params values for catchall correctly",
"getServerSideProps should supply query values SSR",
"getServerSideProps should work with early request ending"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/handle-non-hoisted-swc-helpers/index.test.ts": {
"passed": ["handle-non-hoisted-swc-helpers should work"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/hello-world/hello-world.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"hello-world should work using browser",
"hello-world should work using cheerio",
"hello-world should work with fetch",
"hello-world should work with html"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/i18n-api-support/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n API support should fallback rewrite non-matching API request",
"i18n API support should respond to normal API request",
"i18n API support should respond to normal dynamic API request"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/i18n-data-fetching-redirect/index.test.ts": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n-data-fetching-redirect Redirect to another locale gsp-blocking-redirect en -> sv",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"i18n-data-fetching-redirect Redirect to another locale gsp-blocking-redirect sv -> en",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n-data-fetching-redirect Redirect to another locale gsp-fallback-redirect en -> sv",
"i18n-data-fetching-redirect Redirect to another locale gsp-fallback-redirect sv -> en",
"i18n-data-fetching-redirect Redirect to another locale gssp-redirect en -> sv",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"i18n-data-fetching-redirect Redirect to another locale gssp-redirect sv -> en",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n-data-fetching-redirect Redirect to another locale next/link gsp-blocking-redirect en -> sv",
"i18n-data-fetching-redirect Redirect to another locale next/link gsp-blocking-redirect sv -> en",
"i18n-data-fetching-redirect Redirect to another locale next/link gsp-fallback-redirect en -> sv",
"i18n-data-fetching-redirect Redirect to another locale next/link gsp-fallback-redirect sv -> en",
"i18n-data-fetching-redirect Redirect to another locale next/link gssp-redirect en -> sv",
"i18n-data-fetching-redirect Redirect to another locale next/link gssp-redirect sv -> en",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"i18n-data-fetching-redirect Redirect to locale from context gsp-blocking-redirect en",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n-data-fetching-redirect Redirect to locale from context gsp-blocking-redirect sv",
"i18n-data-fetching-redirect Redirect to locale from context gsp-fallback-redirect en",
"i18n-data-fetching-redirect Redirect to locale from context gsp-fallback-redirect sv",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"i18n-data-fetching-redirect Redirect to locale from context gssp-redirect en",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n-data-fetching-redirect Redirect to locale from context gssp-redirect sv",
"i18n-data-fetching-redirect Redirect to locale from context next/link gsp-blocking-redirect en",
"i18n-data-fetching-redirect Redirect to locale from context next/link gsp-blocking-redirect sv",
"i18n-data-fetching-redirect Redirect to locale from context next/link gsp-fallback-redirect en",
"i18n-data-fetching-redirect Redirect to locale from context next/link gsp-fallback-redirect sv",
"i18n-data-fetching-redirect Redirect to locale from context next/link gssp-redirect en",
"i18n-data-fetching-redirect Redirect to locale from context next/link gssp-redirect sv"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/i18n-data-route/i18n-data-route.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n-data-route with locale prefix /en-CA should render /[slug]/about via /en-CA/blog/about",
"i18n-data-route with locale prefix /en-CA should render /about via /en-CA/about",
"i18n-data-route with locale prefix /en-CA should serve data for /[slug]/about",
"i18n-data-route with locale prefix /en-CA should serve data for /about",
"i18n-data-route with locale prefix /fr-CA should render /[slug]/about via /fr-CA/blog/about",
"i18n-data-route with locale prefix /fr-CA should render /about via /fr-CA/about",
"i18n-data-route with locale prefix /fr-CA should serve data for /[slug]/about",
"i18n-data-route with locale prefix /fr-CA should serve data for /about",
"i18n-data-route without locale prefix should render /[slug]/about via /blog/about",
"i18n-data-route without locale prefix should render /about via /about",
"i18n-data-route without locale prefix should serve data for /[slug]/about",
"i18n-data-route without locale prefix should serve data for /about"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/i18n-default-locale-redirect/i18n-default-locale-redirect.test.ts": {
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"passed": [
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"i18-default-locale-redirect should not request a path prefixed with default locale",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18-default-locale-redirect should request a path prefixed with non-default locale"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/i18n-disallow-multiple-locales/i18n-disallow-multiple-locales.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n-disallow-multiple-locales /en should 200",
"i18n-disallow-multiple-locales /en-US should 200",
"i18n-disallow-multiple-locales /en-US/en should 404",
"i18n-disallow-multiple-locales /en-US/en-US should 404",
"i18n-disallow-multiple-locales /en-US/fr should 404",
"i18n-disallow-multiple-locales /en-US/fr-BE should 404",
"i18n-disallow-multiple-locales /en-US/nl should 404",
"i18n-disallow-multiple-locales /en-US/nl-BE should 404",
"i18n-disallow-multiple-locales /en-US/nl-NL should 404",
"i18n-disallow-multiple-locales /en/en should 404",
"i18n-disallow-multiple-locales /en/en-US should 404",
"i18n-disallow-multiple-locales /en/fr should 404",
"i18n-disallow-multiple-locales /en/fr-BE should 404",
"i18n-disallow-multiple-locales /en/nl should 404",
"i18n-disallow-multiple-locales /en/nl-BE should 404",
"i18n-disallow-multiple-locales /en/nl-NL should 404",
"i18n-disallow-multiple-locales /fr should 200",
"i18n-disallow-multiple-locales /fr-BE should 200",
"i18n-disallow-multiple-locales /fr-BE/en should 404",
"i18n-disallow-multiple-locales /fr-BE/en-US should 404",
"i18n-disallow-multiple-locales /fr-BE/fr should 404",
"i18n-disallow-multiple-locales /fr-BE/fr-BE should 404",
"i18n-disallow-multiple-locales /fr-BE/nl should 404",
"i18n-disallow-multiple-locales /fr-BE/nl-BE should 404",
"i18n-disallow-multiple-locales /fr-BE/nl-NL should 404",
"i18n-disallow-multiple-locales /fr/en should 404",
"i18n-disallow-multiple-locales /fr/en-US should 404",
"i18n-disallow-multiple-locales /fr/fr should 404",
"i18n-disallow-multiple-locales /fr/fr-BE should 404",
"i18n-disallow-multiple-locales /fr/nl should 404",
"i18n-disallow-multiple-locales /fr/nl-BE should 404",
"i18n-disallow-multiple-locales /fr/nl-NL should 404",
"i18n-disallow-multiple-locales /nl should 200",
"i18n-disallow-multiple-locales /nl-BE should 200",
"i18n-disallow-multiple-locales /nl-BE/en should 404",
"i18n-disallow-multiple-locales /nl-BE/en-US should 404",
"i18n-disallow-multiple-locales /nl-BE/fr should 404",
"i18n-disallow-multiple-locales /nl-BE/fr-BE should 404",
"i18n-disallow-multiple-locales /nl-BE/nl should 404",
"i18n-disallow-multiple-locales /nl-BE/nl-BE should 404",
"i18n-disallow-multiple-locales /nl-BE/nl-NL should 404",
"i18n-disallow-multiple-locales /nl-NL should 200",
"i18n-disallow-multiple-locales /nl-NL/en should 404",
"i18n-disallow-multiple-locales /nl-NL/en-US should 404",
"i18n-disallow-multiple-locales /nl-NL/fr should 404",
"i18n-disallow-multiple-locales /nl-NL/fr-BE should 404",
"i18n-disallow-multiple-locales /nl-NL/nl should 404",
"i18n-disallow-multiple-locales /nl-NL/nl-BE should 404",
"i18n-disallow-multiple-locales /nl-NL/nl-NL should 404",
"i18n-disallow-multiple-locales /nl/en should 404",
"i18n-disallow-multiple-locales /nl/en-US should 404",
"i18n-disallow-multiple-locales /nl/fr should 404",
"i18n-disallow-multiple-locales /nl/fr-BE should 404",
"i18n-disallow-multiple-locales /nl/nl should 404",
"i18n-disallow-multiple-locales /nl/nl-BE should 404",
"i18n-disallow-multiple-locales /nl/nl-NL should 404",
"i18n-disallow-multiple-locales should verify the default locale works"
],
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/i18n-ignore-redirect-source-locale/redirects-with-basepath.test.ts": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from and to: ",
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from and to: /en",
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from and to: /nl",
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from and to: /sv",
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from: to: /",
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from: to: en",
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from: to: sv",
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from: /en to: /",
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from: /en to: en",
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from: /en to: sv",
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from: /nl to: /",
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from: /nl to: en",
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from: /nl to: sv",
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from: /sv to: /",
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from: /sv to: en",
"i18n-ignore-redirect-source-locale with basepath get redirected to the new page, from: /sv to: sv"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/i18n-ignore-redirect-source-locale/redirects.test.ts": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n-ignore-redirect-source-locale get redirected to the new page, from and to: ",
"i18n-ignore-redirect-source-locale get redirected to the new page, from and to: /en",
"i18n-ignore-redirect-source-locale get redirected to the new page, from and to: /nl",
"i18n-ignore-redirect-source-locale get redirected to the new page, from and to: /sv",
"i18n-ignore-redirect-source-locale get redirected to the new page, from: to: /",
"i18n-ignore-redirect-source-locale get redirected to the new page, from: to: en",
"i18n-ignore-redirect-source-locale get redirected to the new page, from: to: sv",
"i18n-ignore-redirect-source-locale get redirected to the new page, from: /en to: /",
"i18n-ignore-redirect-source-locale get redirected to the new page, from: /en to: en",
"i18n-ignore-redirect-source-locale get redirected to the new page, from: /en to: sv",
"i18n-ignore-redirect-source-locale get redirected to the new page, from: /nl to: /",
"i18n-ignore-redirect-source-locale get redirected to the new page, from: /nl to: en",
"i18n-ignore-redirect-source-locale get redirected to the new page, from: /nl to: sv",
"i18n-ignore-redirect-source-locale get redirected to the new page, from: /sv to: /",
"i18n-ignore-redirect-source-locale get redirected to the new page, from: /sv to: en",
"i18n-ignore-redirect-source-locale get redirected to the new page, from: /sv to: sv"
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/i18n-ignore-rewrite-source-locale/rewrites-with-basepath.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n-ignore-rewrite-source-locale with basepath call api by skipping locale in rewrite, locale: ",
"i18n-ignore-rewrite-source-locale with basepath call api by skipping locale in rewrite, locale: /en",
"i18n-ignore-rewrite-source-locale with basepath call api by skipping locale in rewrite, locale: /nl",
"i18n-ignore-rewrite-source-locale with basepath call api by skipping locale in rewrite, locale: /sv",
"i18n-ignore-rewrite-source-locale with basepath get public file by skipping locale in rewrite, locale: ",
"i18n-ignore-rewrite-source-locale with basepath get public file by skipping locale in rewrite, locale: /en",
"i18n-ignore-rewrite-source-locale with basepath get public file by skipping locale in rewrite, locale: /nl",
"i18n-ignore-rewrite-source-locale with basepath get public file by skipping locale in rewrite, locale: /sv"
],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n-ignore-rewrite-source-locale with basepath get _next/static/ files by skipping locale in rewrite, locale: ",
"i18n-ignore-rewrite-source-locale with basepath get _next/static/ files by skipping locale in rewrite, locale: /en",
"i18n-ignore-rewrite-source-locale with basepath get _next/static/ files by skipping locale in rewrite, locale: /nl",
"i18n-ignore-rewrite-source-locale with basepath get _next/static/ files by skipping locale in rewrite, locale: /sv"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/i18n-ignore-rewrite-source-locale/rewrites.test.ts": {
"passed": [
"i18n-ignore-rewrite-source-locale call api by skipping locale in rewrite, locale: ",
"i18n-ignore-rewrite-source-locale call api by skipping locale in rewrite, locale: /en",
"i18n-ignore-rewrite-source-locale call api by skipping locale in rewrite, locale: /nl",
"i18n-ignore-rewrite-source-locale call api by skipping locale in rewrite, locale: /sv",
"i18n-ignore-rewrite-source-locale get public file by skipping locale in rewrite, locale: ",
"i18n-ignore-rewrite-source-locale get public file by skipping locale in rewrite, locale: /en",
"i18n-ignore-rewrite-source-locale get public file by skipping locale in rewrite, locale: /nl",
"i18n-ignore-rewrite-source-locale get public file by skipping locale in rewrite, locale: /sv"
],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n-ignore-rewrite-source-locale get _next/static/ files by skipping locale in rewrite, locale: ",
"i18n-ignore-rewrite-source-locale get _next/static/ files by skipping locale in rewrite, locale: /en",
"i18n-ignore-rewrite-source-locale get _next/static/ files by skipping locale in rewrite, locale: /nl",
"i18n-ignore-rewrite-source-locale get _next/static/ files by skipping locale in rewrite, locale: /sv"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/ignore-invalid-popstateevent/with-i18n.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"i18n: Event with stale state - static route previously was dynamic Don't ignore event with different locale",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n: Event with stale state - static route previously was dynamic Ignore event with query param",
"i18n: Event with stale state - static route previously was dynamic Ignore event without query param"
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/ignore-invalid-popstateevent/without-i18n.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Event with stale state - static route previously was dynamic Ignore event with query param",
"Event with stale state - static route previously was dynamic Ignore event without query param"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/instrumentation-hook-src/instrumentation-hook-src.test.ts": {
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"passed": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"instrumentation-hook-rsc instrumentation should not overlap with a instrumentation page",
"instrumentation-hook-rsc instrumentation should run the edge instrumentation compiled version with the edge runtime",
"instrumentation-hook-rsc instrumentation should run the instrumentation hook"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
"pending": [
"instrumentation-hook-rsc instrumentation should reload the server when the instrumentation hook changes"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"runtimeError": false
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
},
"test/e2e/instrumentation-hook/instrumentation-hook.test.ts": {
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Instrumentation Hook general should not overlap with a instrumentation page",
"Instrumentation Hook with-async-edge-page with-async-edge-page should run the instrumentation hook",
"Instrumentation Hook with-async-node-page with-async-node-page should run the instrumentation hook",
"Instrumentation Hook with-edge-api with-edge-api should run the instrumentation hook",
"Instrumentation Hook with-edge-page with-edge-page should run the instrumentation hook",
"Instrumentation Hook with-middleware with-middleware should run the instrumentation hook",
"Instrumentation Hook with-node-api with-node-api should run the instrumentation hook",
"Instrumentation Hook with-node-page with-node-page should run the instrumentation hook"
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
"pending": [
"Instrumentation Hook general should reload the server when the instrumentation hook changes"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/link-with-api-rewrite/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"link-with-api-rewrite should perform hard navigation for direct urls",
"link-with-api-rewrite should perform hard navigation for rewritten urls"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/manual-client-base-path/index.test.ts": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"manual-client-base-path should navigate correctly from another",
"manual-client-base-path should navigate correctly from index",
"manual-client-base-path should not update with basePath on mount /",
"manual-client-base-path should not update with basePath on mount /another",
"manual-client-base-path should not update with basePath on mount /dynamic/first",
"manual-client-base-path should not update with basePath on mount /dynamic/second",
"manual-client-base-path should not warn for flag in output"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/middleware-base-path/test/index.test.ts": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [
"Middleware base tests router.query must exist when Link clicked page routing",
"Middleware base tests should execute from absolute paths"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/middleware-custom-matchers-basepath/test/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware custom matchers basePath should match",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Middleware custom matchers basePath should match has query on client routing",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware custom matchers basePath should not match"
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/middleware-custom-matchers-i18n/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware custom matchers i18n should match",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Middleware custom matchers i18n should match has query on client routing",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware custom matchers i18n should not match",
"Middleware custom matchers with root should not match"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/middleware-custom-matchers/test/index.test.ts": {
"passed": [
"Middleware custom matchers should match has cookie",
"Middleware custom matchers should match has cookie on client routing",
"Middleware custom matchers should match has header",
"Middleware custom matchers should match has header value",
"Middleware custom matchers should match has host",
"Middleware custom matchers should match has query",
"Middleware custom matchers should match has query on client routing",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware custom matchers should match missing header correctly",
"Middleware custom matchers should match missing query correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware custom matchers should match source path"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/middleware-dynamic-basepath-matcher/test/index.test.ts": {
"passed": [
"Middleware custom matchers basePath should match",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"Middleware custom matchers basePath should match query path",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware custom matchers basePath should not match"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/middleware-fetches-with-any-http-method/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware fetches with any HTTP method passes the method on a direct fetch request",
"Middleware fetches with any HTTP method passes the method when providing a Request object"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/middleware-fetches-with-body/index.test.ts": {
"passed": [
"Middleware fetches with body should return 413 for body equal to 10mb",
"Middleware fetches with body with bodyParser = false should be able to send and return with body greater than 16KiB",
"Middleware fetches with body with bodyParser = false should be able to send and return with body size equal to 16KiB",
"Middleware fetches with body with custom bodyParser sizeLimit (5kb) should be able to send and return body size equal to 5kb",
"Middleware fetches with body with custom bodyParser sizeLimit (5kb) should return 413 for body greater than 5kb",
"Middleware fetches with body with custom bodyParser sizeLimit (5mb) should be able to send and return body size equal to 5mb",
"Middleware fetches with body with custom bodyParser sizeLimit (5mb) should return 413 for body greater than 5mb",
"Middleware fetches with body with default bodyParser sizeLimit (1mb) should be able to send and return body greater than default highWaterMark (16KiB)",
"Middleware fetches with body with default bodyParser sizeLimit (1mb) should be able to send and return body size equal to 1mb",
"Middleware fetches with body with default bodyParser sizeLimit (1mb) should return 413 for body greater than 1mb"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/middleware-general/test/index.test.ts": {
"passed": [
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Middleware Runtime with i18n allows shallow linking with middleware",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware Runtime with i18n allows to access env variables",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware Runtime with i18n hard-navigates when the data request failed",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"Middleware Runtime with i18n passes search params with rewrites",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"Middleware Runtime with i18n refreshes the page when middleware changes ",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware Runtime with i18n should accept a URL instance for fetch",
"Middleware Runtime with i18n should add a rewrite header on data requests for rewrites",
"Middleware Runtime with i18n should allow to abort a fetch request",
"Middleware Runtime with i18n should be able to rewrite on _next/static/chunks/pages/ 404",
"Middleware Runtime with i18n should contain `globalThis`",
"Middleware Runtime with i18n should contain crypto APIs",
"Middleware Runtime with i18n should have correct dynamic route params for middleware rewrite to dynamic route",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware Runtime with i18n should have correct dynamic route params on client-transition to dynamic route",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Middleware Runtime with i18n should have correct query values for rewrite to ssg page",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Middleware Runtime with i18n should have correct route params for chained rewrite from middleware to config rewrite",
"Middleware Runtime with i18n should have correct route params for rewrite from config dynamic route",
"Middleware Runtime with i18n should have correct route params for rewrite from config non-dynamic route",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"Middleware Runtime with i18n should have init header for NextResponse.redirect",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware Runtime with i18n should keep non data requests in their original shape",
"Middleware Runtime with i18n should normalize data requests into page requests",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware Runtime with i18n should only contain middleware route in dev middleware manifest",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Middleware Runtime with i18n should redirect the same for direct visit and client-transition",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware Runtime with i18n should respond with 400 on decode failure",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Middleware Runtime with i18n should rewrite correctly for non-SSG/SSP page",
"Middleware Runtime with i18n should rewrite the same for direct visit and client-transition",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware Runtime with i18n should set fetch user agent correctly",
"Middleware Runtime with i18n should throw when using NextRequest with a relative URL",
"Middleware Runtime with i18n should throw when using NextResponse.rewrite with a relative URL",
"Middleware Runtime with i18n should throw when using Request with a relative URL",
"Middleware Runtime with i18n should throw when using URL with a relative URL",
"Middleware Runtime with i18n should trigger middleware for data requests",
"Middleware Runtime with i18n should validate & parse request url from a dynamic route with params",
"Middleware Runtime with i18n should validate & parse request url from a dynamic route with params and no query",
"Middleware Runtime with i18n should validate & parse request url from a dynamic route with params and query",
"Middleware Runtime with i18n should validate & parse request url from any route",
"Middleware Runtime with i18n should warn when using NextResponse.redirect with a relative URL",
"Middleware Runtime with i18n should warn when using Response.redirect with a relative URL",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Middleware Runtime with i18n should work with notFound: true correctly",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Middleware Runtime without i18n allows shallow linking with middleware",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware Runtime without i18n allows to access env variables",
"Middleware Runtime without i18n hard-navigates when the data request failed",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"Middleware Runtime without i18n passes search params with rewrites",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"Middleware Runtime without i18n refreshes the page when middleware changes ",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware Runtime without i18n should accept a URL instance for fetch",
"Middleware Runtime without i18n should add a rewrite header on data requests for rewrites",
"Middleware Runtime without i18n should allow to abort a fetch request",
"Middleware Runtime without i18n should be able to rewrite on _next/static/chunks/pages/ 404",
"Middleware Runtime without i18n should contain `globalThis`",
"Middleware Runtime without i18n should contain crypto APIs",
"Middleware Runtime without i18n should have correct dynamic route params for middleware rewrite to dynamic route",
"Middleware Runtime without i18n should have correct dynamic route params on client-transition to dynamic route",
"Middleware Runtime without i18n should have correct query values for rewrite to ssg page",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Middleware Runtime without i18n should have correct route params for chained rewrite from middleware to config rewrite",
"Middleware Runtime without i18n should have correct route params for rewrite from config dynamic route",
"Middleware Runtime without i18n should have correct route params for rewrite from config non-dynamic route",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"Middleware Runtime without i18n should have init header for NextResponse.redirect",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware Runtime without i18n should keep non data requests in their original shape",
"Middleware Runtime without i18n should normalize data requests into page requests",
"Middleware Runtime without i18n should only contain middleware route in dev middleware manifest",
"Middleware Runtime without i18n should redirect the same for direct visit and client-transition",
"Middleware Runtime without i18n should respond with 400 on decode failure",
"Middleware Runtime without i18n should rewrite correctly for non-SSG/SSP page",
"Middleware Runtime without i18n should rewrite the same for direct visit and client-transition",
"Middleware Runtime without i18n should set fetch user agent correctly",
"Middleware Runtime without i18n should throw when using NextRequest with a relative URL",
"Middleware Runtime without i18n should throw when using NextResponse.rewrite with a relative URL",
"Middleware Runtime without i18n should throw when using Request with a relative URL",
"Middleware Runtime without i18n should throw when using URL with a relative URL",
"Middleware Runtime without i18n should trigger middleware for data requests",
"Middleware Runtime without i18n should validate & parse request url from a dynamic route with params and query",
"Middleware Runtime without i18n should validate & parse request url from any route",
"Middleware Runtime without i18n should warn when using NextResponse.redirect with a relative URL",
"Middleware Runtime without i18n should warn when using Response.redirect with a relative URL",
"Middleware Runtime without i18n should work with notFound: true correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/middleware-matcher/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware can set the matcher in its config adds the header for a matched data path (with header)",
"Middleware can set the matcher in its config adds the header for a matched data path (without header)",
"Middleware can set the matcher in its config adds the header for a matched path",
"Middleware can set the matcher in its config adds the header for another matched data path",
"Middleware can set the matcher in its config adds the header for another matched path",
"Middleware can set the matcher in its config does add the header for root data request",
"Middleware can set the matcher in its config does add the header for root request",
"Middleware can set the matcher in its config should load matches in client matchers correctly",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware can set the matcher in its config should navigate correctly with matchers",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"using a single matcher adds the header for a matched data path (without header)",
"using a single matcher adds the header for a matched path",
"using a single matcher adds the headers for a matched data path (with header)",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"using a single matcher does not add the header for an unmatched path",
"using a single matcher does not add the header for root data request",
"using a single matcher does not add the header for root request",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"using a single matcher with i18n adds the header for a matched path",
"using a single matcher with i18n adds the header for a mathed root path with /index",
"using a single matcher with i18n adds the headers for a matched data path",
"using a single matcher with i18n and basePath adds the header for a matched path",
"using a single matcher with i18n and basePath adds the header for a mathed root path with /index",
"using a single matcher with i18n and basePath adds the headers for a matched data path",
"using a single matcher with i18n and basePath and trailingSlash adds the header for a matched path",
"using a single matcher with i18n and basePath and trailingSlash adds the header for a mathed root path with /index",
"using a single matcher with i18n and basePath and trailingSlash adds the headers for a matched data path",
"using a single matcher with i18n and basePath and trailingSlash does not add the header for an unmatched path",
"using a single matcher with i18n and basePath does not add the header for an unmatched path",
"using a single matcher with i18n and trailingSlash adds the header for a matched path",
"using a single matcher with i18n and trailingSlash adds the header for a mathed root path with /index",
"using a single matcher with i18n and trailingSlash adds the headers for a matched data path",
"using a single matcher with i18n and trailingSlash does not add the header for an unmatched path",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"using a single matcher with i18n does not add the header for an unmatched path",
"using root matcher adds the header for a matched data path (with header)",
"using root matcher adds the header for a matched data path (without header)",
"using root matcher adds the header to the /",
"using root matcher adds the header to the /index"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/middleware-redirects/test/index.test.ts": {
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"passed": [
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Middleware Redirect /fr should implement internal redirects",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware Redirect /fr should redirect",
"Middleware Redirect /fr should redirect (infinite-loop)",
"Middleware Redirect /fr should redirect cleanly with the original url param",
"Middleware Redirect /fr should redirect multiple times",
"Middleware Redirect /fr should redirect to api route with locale",
"Middleware Redirect /fr should redirect with a fragment",
"Middleware Redirect does not include the locale in redirects by default",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Middleware Redirect should implement internal redirects",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware Redirect should redirect",
"Middleware Redirect should redirect (infinite-loop)",
"Middleware Redirect should redirect cleanly with the original url param",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware Redirect should redirect correctly with redirect in next.config.js",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware Redirect should redirect multiple times",
"Middleware Redirect should redirect to api route with locale",
"Middleware Redirect should redirect to data urls with data requests and internal redirects",
"Middleware Redirect should redirect to external urls with data requests and external redirects",
"Middleware Redirect should redirect with a fragment"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"runtimeError": false
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
},
"test/e2e/middleware-request-header-overrides/test/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware Request Headers Overrides Edge Functions Backend Adds new headers",
"Middleware Request Headers Overrides Edge Functions Backend Deletes headers",
"Middleware Request Headers Overrides Edge Functions Backend Updates headers",
"Middleware Request Headers Overrides Serverless Functions Backend Adds new headers",
"Middleware Request Headers Overrides Serverless Functions Backend Deletes headers",
"Middleware Request Headers Overrides Serverless Functions Backend Updates headers",
"Middleware Request Headers Overrides getServerSideProps Backend Adds new headers",
"Middleware Request Headers Overrides getServerSideProps Backend Deletes headers",
"Middleware Request Headers Overrides getServerSideProps Backend Updates headers"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/middleware-responses/test/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware Responses /fr responds with multiple cookies",
"Middleware Responses /fr should not fail when returning a stream",
"Middleware Responses /fr should not fail when returning a text body",
"Middleware Responses /fr should respond appending headers headers",
"Middleware Responses /fr should respond with a 401 status code",
"Middleware Responses /fr should respond with one header",
"Middleware Responses /fr should respond with two headers",
"Middleware Responses responds with multiple cookies",
"Middleware Responses should not fail when returning a stream",
"Middleware Responses should not fail when returning a text body",
"Middleware Responses should respond appending headers headers",
"Middleware Responses should respond with a 401 status code",
"Middleware Responses should respond with one header",
"Middleware Responses should respond with two headers"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
"runtimeError": false
},
"test/e2e/middleware-rewrites/test/index.test.ts": {
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"passed": [
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Middleware Rewrite /fr can rewrite from path with colon",
"Middleware Rewrite /fr can rewrite from path with colon and retain query parameter",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Middleware Rewrite /fr can rewrite to path with colon",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Middleware Rewrite /fr can rewrite to path with colon and retain query parameter",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Middleware Rewrite /fr should add a cookie and rewrite to a/b test",
"Middleware Rewrite /fr should clear query parameters",
"Middleware Rewrite /fr should correctly rewriting to a different dynamic path",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware Rewrite /fr should not call middleware with shallow push",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Middleware Rewrite /fr should rewrite to Vercel",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Middleware Rewrite /fr should rewrite to about page",
"Middleware Rewrite /fr should rewrite when not using localhost",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Middleware Rewrite /fr should rewrite without hard navigation",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware Rewrite /fr support colons in path",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Middleware Rewrite can rewrite from path with colon",
"Middleware Rewrite can rewrite from path with colon and retain query parameter",
"Middleware Rewrite can rewrite to path with colon",
"Middleware Rewrite can rewrite to path with colon and retain query parameter",
"Middleware Rewrite should add a cookie and rewrite to a/b test",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Middleware Rewrite should allow to opt-out prefetch caching",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Middleware Rewrite should allow to rewrite keeping the locale in pathname",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Middleware Rewrite should allow to rewrite to a `afterFiles` rewrite config",
"Middleware Rewrite should allow to rewrite to a `beforeFiles` rewrite config",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Middleware Rewrite should allow to rewrite to a different locale",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Middleware Rewrite should allow to switch locales",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Middleware Rewrite should behave consistently on recursive rewrites",
"Middleware Rewrite should clear query parameters",
"Middleware Rewrite should correctly rewriting to a different dynamic path",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Middleware Rewrite should handle middleware rewrite with body correctly",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware Rewrite should handle next.config.js rewrite with body correctly",
"Middleware Rewrite should handle shallow navigation correctly (dynamic page)",
"Middleware Rewrite should handle shallow navigation correctly (non-dynamic page)",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Middleware Rewrite should handle static dynamic rewrite from middleware correctly",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Middleware Rewrite should handle static rewrite from next.config.js correctly",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware Rewrite should hard navigate on 404 for data request",
"Middleware Rewrite should have correct query info for dynamic route after query hydration",
"Middleware Rewrite should not call middleware with shallow push",
"Middleware Rewrite should not have un-necessary data request on rewrite",
"Middleware Rewrite should not have unexpected errors",
"Middleware Rewrite should not mix component cache when navigating between dynamic routes",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Middleware Rewrite should override with rewrite externally correctly",
"Middleware Rewrite should override with rewrite internally correctly",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Middleware Rewrite should resolve dynamic route after rewrite correctly",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware Rewrite should return HTML/data correctly for pre-rendered page",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Middleware Rewrite should rewrite correctly when navigating via history",
"Middleware Rewrite should rewrite correctly when navigating via history after query update",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Middleware Rewrite should rewrite to Vercel",
"Middleware Rewrite should rewrite to about page",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Middleware Rewrite should rewrite to data urls for incoming data request internally rewritten",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Middleware Rewrite should rewrite to fallback: true page successfully",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Middleware Rewrite should rewrite to the external url for incoming data request externally rewritten",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Middleware Rewrite should rewrite when not using localhost",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Middleware Rewrite should rewrite without hard navigation",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware Rewrite support colons in path"
],
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"failed": [],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"pending": [
"Middleware Rewrite includes the locale in rewrites by default"
],
"flakey": [
"Middleware Rewrite should have props for afterFiles rewrite to SSG page"
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/middleware-shallow-link/index.test.ts": {
"passed": ["browser-shallow-navigation should render the correct page"],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/e2e/middleware-trailing-slash/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Middleware Runtime trailing slash allows shallow linking with middleware",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"Middleware Runtime trailing slash refreshes the page when middleware changes ",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware Runtime trailing slash should add a rewrite header on data requests for rewrites",
"Middleware Runtime trailing slash should have correct dynamic route params for middleware rewrite to dynamic route",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Middleware Runtime trailing slash should have correct dynamic route params on client-transition to dynamic route",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"Middleware Runtime trailing slash should have correct query values for rewrite to ssg page",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Middleware Runtime trailing slash should have correct route params for chained rewrite from middleware to config rewrite",
"Middleware Runtime trailing slash should have correct route params for rewrite from config dynamic route",
"Middleware Runtime trailing slash should have correct route params for rewrite from config non-dynamic route",
"Middleware Runtime trailing slash should have init header for NextResponse.redirect",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware Runtime trailing slash should keep non data requests in their original shape",
"Middleware Runtime trailing slash should normalize data requests into page requests",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware Runtime trailing slash should redirect the same for direct visit and client-transition",
"Middleware Runtime trailing slash should respond with 400 on decode failure",
"Middleware Runtime trailing slash should rewrite correctly for non-SSG/SSP page",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Middleware Runtime trailing slash should rewrite the same for direct visit and client-transition",
"Middleware Runtime trailing slash should trigger middleware for data requests",
"Middleware Runtime trailing slash should validate & parse request url from any route",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware Runtime trailing slash with .html extension should work using browser",
"Middleware Runtime trailing slash with .html extension should work when navigating",
"Middleware Runtime trailing slash with .html extension should work when requesting the page directly",
"Middleware Runtime trailing slash without .html extension should work using browser",
"Middleware Runtime trailing slash without .html extension should work when navigating",
"Middleware Runtime trailing slash without .html extension should work when requesting the page directly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/module-layer/index.test.ts": {
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
update manifest (#57523) update test manifest from daily test run Closes WEB-1889
2023-10-26 22:35:50 +02:00
"module layer no server-only in server targets should render routes marked with restriction marks without errors",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"module layer with server-only in server targets should render routes marked with restriction marks without errors"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/multi-zone/multi-zone.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [
Update Turbopack test manifest (#60413) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-09 10:32:10 +01:00
"multi-zone should correctly respond for /",
"multi-zone should correctly respond for /blog/post-1",
"multi-zone should correctly respond for /guest",
"multi-zone should correctly respond for /guest/another/post-1",
"multi-zone should correctly respond for /guest/blog/post-1",
Update Turbopack test manifest (#59356) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-07 15:51:45 +01:00
"multi-zone should support HMR in both apps"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/new-link-behavior/child-a-tag-error.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"New Link Behavior with <a> child should throw error with <a> child"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/new-link-behavior/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"New Link Behavior should handle onclick",
"New Link Behavior should handle preventdefault",
"New Link Behavior should navigate to /about",
"New Link Behavior should render link with <a>",
"New Link Behavior should render link with classname",
"New Link Behavior should render link with id",
"New Link Behavior should render link with multiple children"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/new-link-behavior/material-ui.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"New Link Behavior with material-ui should render MuiLink with <a>"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/new-link-behavior/stitches.test.ts": {
"passed": ["New Link Behavior with stitches should render <a>"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/new-link-behavior/typescript.test.ts": {
"passed": [
"New Link Behavior should apply ref on link",
"New Link Behavior should render link with <a>"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/next-font/basepath.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": ["next/font/google basepath preload correct files"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/next-font/google-fetch-error.test.ts": {
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/font/google fetch error should use a fallback font in dev"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/next-font/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/font app computed styles page using fallback fonts",
"next/font app computed styles page using variables",
"next/font app computed styles page with fonts",
"next/font app import values Variable font without weight range",
"next/font app import values page with font",
"next/font app import values page with local fonts",
"next/font app-old computed styles page using fallback fonts",
"next/font app-old computed styles page using variables",
"next/font app-old computed styles page with fonts",
"next/font app-old import values Variable font without weight range",
"next/font app-old import values page with font",
"next/font app-old import values page with local fonts"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Turbopack: Align some "Module not found" errors with webpack (#58518) This: - Sends an hmr sync event so that errors that occur after the initial hmr connection are sent to the client - Aligns on `path/to/file.js:line:column` format across error overlay implementations in the cli and on the web - Adapts "Module not found" errors from Turbopack to include Next.js-relevant formatting and documentation links to align with webpack Test Plan: Passes 3 tests that were previously failing Closes PACK-1974 --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by: Leah <github.leah@hrmny.sh> Co-authored-by: Zack Tanner <zacktanner@gmail.com>
2023-11-30 17:34:56 +01:00
"next/font app Fallback fontfaces google Fraunces",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/font app Fallback fontfaces google Indie flower",
Turbopack: Align some "Module not found" errors with webpack (#58518) This: - Sends an hmr sync event so that errors that occur after the initial hmr connection are sent to the client - Aligns on `path/to/file.js:line:column` format across error overlay implementations in the cli and on the web - Adapts "Module not found" errors from Turbopack to include Next.js-relevant formatting and documentation links to align with webpack Test Plan: Passes 3 tests that were previously failing Closes PACK-1974 --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by: Leah <github.leah@hrmny.sh> Co-authored-by: Zack Tanner <zacktanner@gmail.com>
2023-11-30 17:34:56 +01:00
"next/font app Fallback fontfaces local Fraunces",
"next/font app Fallback fontfaces local Indie flower",
"next/font app Fallback fontfaces local Roboto multiple weights and styles",
"next/font app Fallback fontfaces local Roboto multiple weights and styles - variable 1",
"next/font app Fallback fontfaces local Roboto multiple weights and styles - variable 2",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/font app preload font without preloadable subsets",
"next/font app preload font without size adjust",
"next/font app preload google fonts with multiple weights/styles",
"next/font app preload page with fonts",
"next/font app preload page with local fonts",
"next/font app preload page without fonts",
fix: cache next font during development to avoid FOUC (#60175) In fact, this is an issue that has been solved in #52033, but it seems #52492 introduced it again. > During development, for fonts created via next/font the file path is already containing the hash so we can always have them cached. This fixes the problem of fonts causing FOUC in HMR. Fixes #50782 --------- Co-authored-by: Tim Neutkens <tim@timneutkens.nl>
2024-01-04 09:54:23 +01:00
"next/font app should use production cache control for fonts",
Turbopack: Align some "Module not found" errors with webpack (#58518) This: - Sends an hmr sync event so that errors that occur after the initial hmr connection are sent to the client - Aligns on `path/to/file.js:line:column` format across error overlay implementations in the cli and on the web - Adapts "Module not found" errors from Turbopack to include Next.js-relevant formatting and documentation links to align with webpack Test Plan: Passes 3 tests that were previously failing Closes PACK-1974 --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by: Leah <github.leah@hrmny.sh> Co-authored-by: Zack Tanner <zacktanner@gmail.com>
2023-11-30 17:34:56 +01:00
"next/font app-old Fallback fontfaces google Fraunces",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/font app-old Fallback fontfaces google Indie flower",
Turbopack: Align some "Module not found" errors with webpack (#58518) This: - Sends an hmr sync event so that errors that occur after the initial hmr connection are sent to the client - Aligns on `path/to/file.js:line:column` format across error overlay implementations in the cli and on the web - Adapts "Module not found" errors from Turbopack to include Next.js-relevant formatting and documentation links to align with webpack Test Plan: Passes 3 tests that were previously failing Closes PACK-1974 --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com> Co-authored-by: Leah <github.leah@hrmny.sh> Co-authored-by: Zack Tanner <zacktanner@gmail.com>
2023-11-30 17:34:56 +01:00
"next/font app-old Fallback fontfaces local Fraunces",
"next/font app-old Fallback fontfaces local Indie flower",
"next/font app-old Fallback fontfaces local Roboto multiple weights and styles",
"next/font app-old Fallback fontfaces local Roboto multiple weights and styles - variable 1",
"next/font app-old Fallback fontfaces local Roboto multiple weights and styles - variable 2",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/font app-old preload font without preloadable subsets",
"next/font app-old preload font without size adjust",
"next/font app-old preload google fonts with multiple weights/styles",
"next/font app-old preload page with fonts",
"next/font app-old preload page with local fonts",
fix: cache next font during development to avoid FOUC (#60175) In fact, this is an issue that has been solved in #52033, but it seems #52492 introduced it again. > During development, for fonts created via next/font the file path is already containing the hash so we can always have them cached. This fixes the problem of fonts causing FOUC in HMR. Fixes #50782 --------- Co-authored-by: Tim Neutkens <tim@timneutkens.nl>
2024-01-04 09:54:23 +01:00
"next/font app-old preload page without fonts",
"next/font app-old should use production cache control for fonts"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/next-font/with-font-declarations-file.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/font/google with-font-declarations-file preload correct files at /inter",
"next/font/google with-font-declarations-file preload correct files at /local-font",
"next/font/google with-font-declarations-file preload correct files at /roboto"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/next-font/with-proxy.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/font/google with proxy should use a proxy agent when proxy environment variable is set"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/next-font/without-preloaded-fonts.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/font/google without-preloaded-fonts without _app without fonts"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/font/google no preloads with _app without fonts",
"next/font/google no preloads with _app without preload",
"next/font/google without-preloaded-fonts without _app without preload"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/next-head/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"next/head should have correct head tags after hydration",
"next/head should have correct head tags from a fragment",
"next/head should have correct head tags in initial document",
"next/head should have current head tags from a _document getInitialProps",
"next/head should place charset element at the top of <head>"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/next-image-forward-ref/index.test.ts": {
"passed": [
"next-image-forward-ref allows framer-motion to animate opacity"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/next-script/index.test.ts": {
"passed": [
"beforeInteractive in document Head Script is injected server-side",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"beforeInteractive in document body Script is injected server-side"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
"pending": [
"experimental.nextScriptWorkers experimental.nextScriptWorkers: false with no Partytown dependency Partytown snippet is not injected to head if not enabled in configuration",
"experimental.nextScriptWorkers experimental.nextScriptWorkers: true with config override Partytown config script is overwritten",
"experimental.nextScriptWorkers experimental.nextScriptWorkers: true with required Partytown dependency for external script Partytown snippets are injected to head if enabled in configuration",
"experimental.nextScriptWorkers experimental.nextScriptWorkers: true with required Partytown dependency for external script Worker scripts are modified by Partytown to execute on a worker thread",
"experimental.nextScriptWorkers experimental.nextScriptWorkers: true with required Partytown dependency for inline script Inline worker script through children is modified by Partytown to execute on a worker thread",
"experimental.nextScriptWorkers experimental.nextScriptWorkers: true with required Partytown dependency for inline script Inline worker script through dangerouslySetInnerHtml is modified by Partytown to execute on a worker thread"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"runtimeError": false
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
},
"test/e2e/no-eslint-warn-with-no-eslint-config/index.test.ts": {
"passed": [
"no-eslint-warn-with-no-eslint-config should not have eslint warnings when no eslint config",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"no-eslint-warn-with-no-eslint-config should render"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/nonce-head-manager/index.test.ts": {
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"nonce head manager should not re-execute the script when re-rendering",
"nonce head manager should not re-execute the script when re-rendering with CSP header"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": true
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/og-api/index.test.ts": {
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"passed": [
"og-api should respond from index",
enable e2e tests with turbopack (#57432) Closes WEB-1862 --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-10-25 19:46:31 +02:00
"og-api should throw error when returning a response object in pages/api in node runtime",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"og-api should work in app route in node runtime"
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"og-api should work in app route",
"og-api should work in pages/api"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/opentelemetry/opentelemetry.test.ts": {
"passed": [],
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"failed": [],
"pending": [
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"opentelemetry incoming context propagation app router should handle RSC with fetch",
"opentelemetry incoming context propagation app router should handle route handlers in app router",
"opentelemetry incoming context propagation pages should handle api routes in pages",
"opentelemetry incoming context propagation pages should handle getServerSideProps",
"opentelemetry incoming context propagation pages should handle getStaticProps when fallback: 'blocking'",
"opentelemetry root context app router should handle RSC with fetch",
"opentelemetry root context app router should handle route handlers in app router",
"opentelemetry root context pages should handle api routes in pages",
"opentelemetry root context pages should handle getServerSideProps",
"opentelemetry root context pages should handle getStaticProps when fallback: 'blocking'"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/optimized-loading/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Optimized loading page / should load scripts with defer in head",
"Optimized loading page / should not have JS preload links",
"Optimized loading page / should render the page /",
"Optimized loading page /page1 should load scripts with defer in head",
"Optimized loading page /page1 should not have JS preload links",
"Optimized loading page /page1 should render the page /page1"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/pages-performance-mark/index.test.ts": {
"passed": [
"pages performance mark should render the page correctly without crashing with performance mark"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/postcss-config-cjs/index.test.ts": {
"passed": ["postcss-config-cjs works with postcss.config.cjs files"],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/e2e/prerender-crawler.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Prerender crawler handling should block for crawler correctly",
"Prerender crawler handling should return fallback for non-crawler correctly",
"Prerender crawler handling should return prerendered page for correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/prerender-native-module.test.ts": {
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"prerender native module should render /blog/first correctly",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"prerender native module should render /blog/second correctly",
"prerender native module should render index correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/prerender.test.ts": {
"passed": [
"Prerender should 404 for a missing catchall explicit route",
"Prerender should 404 for an invalid data url",
"Prerender should SSR blocking path correctly (blocking)",
"Prerender should SSR blocking path correctly (pre-rendered)",
"Prerender should SSR catch-all page with brackets in param as object",
"Prerender should SSR catch-all page with brackets in param as string",
"Prerender should SSR dynamic page with brackets in param as object",
"Prerender should SSR dynamic page with brackets in param as string",
"Prerender should SSR incremental page correctly",
"Prerender should SSR normal page correctly",
"Prerender should allow rewriting to SSG page with fallback: 'blocking'",
"Prerender should allow rewriting to SSG page with fallback: false",
"Prerender should always call getStaticProps without caching in dev",
"Prerender should always show fallback for page not in getStaticPaths",
"Prerender should error on bad object from getStaticProps",
"Prerender should error on dynamic page without getStaticPaths",
"Prerender should error on dynamic page without getStaticPaths returning fallback property",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Prerender should fetch /_next/data correctly with mismatched href and as",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Prerender should handle fallback only page correctly HTML",
"Prerender should handle fallback only page correctly data",
"Prerender should have gsp in __NEXT_DATA__",
"Prerender should log error in console and browser in dev mode",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Prerender should navigate between pages successfully",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Prerender should navigate to a normal page and back",
"Prerender should navigate to catch-all page with brackets in param as object",
"Prerender should navigate to catch-all page with brackets in param as string",
"Prerender should navigate to dynamic page with brackets in param as object",
"Prerender should navigate to dynamic page with brackets in param as string",
"Prerender should never show fallback for page not in getStaticPaths when blocking",
"Prerender should not contain headers already sent error",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Prerender should not error when rewriting to fallback dynamic SSG page",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Prerender should not fail to update incremental cache",
"Prerender should not fallback before invalid JSON is returned from getStaticProps when blocking fallback",
"Prerender should not have attempted sending invalid payload",
"Prerender should not have experimental undici warning",
"Prerender should not have gsp in __NEXT_DATA__ for non-GSP page",
"Prerender should not re-call getStaticProps when updating query",
"Prerender should not return data for fallback: false and missing dynamic page",
"Prerender should not show fallback for page in getStaticPaths",
"Prerender should not show fallback for page in getStaticPaths when blocking",
"Prerender should not show warning from url prop being returned",
"Prerender should not supply query values to params in /_next/data request",
"Prerender should not supply query values to params or useRouter dynamic page SSR",
"Prerender should not supply query values to params or useRouter non-dynamic page SSR",
"Prerender should parse query values on mount correctly",
"Prerender should reload page on failed data request",
"Prerender should render correctly for SSG pages that starts with api-docs",
"Prerender should respond for catch-all deep folder",
"Prerender should respond with 405 for POST to static page",
"Prerender should return data correctly",
"Prerender should return data correctly for SSG pages that starts with api-docs",
"Prerender should return data correctly for dynamic page",
"Prerender should return data correctly for dynamic page (non-seeded)",
"Prerender should server prerendered path correctly for SSG pages that starts with api-docs",
"Prerender should show error for invalid JSON returned from getStaticProps on CST",
"Prerender should show error for invalid JSON returned from getStaticProps on SSR",
"Prerender should show fallback before invalid JSON is returned from getStaticProps",
"Prerender should show warning every time page with large amount of page data is returned",
"Prerender should show warning when large amount of page data is returned",
"Prerender should support lazy catchall route",
"Prerender should support nested lazy catchall route",
"Prerender should support prerendered catchall route",
"Prerender should support prerendered catchall-explicit route (nested)",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Prerender should support prerendered catchall-explicit route (single)"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/proxy-request-with-middleware/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Requests not effected when middleware used should proxy GET request ",
"Requests not effected when middleware used should proxy POST request with body"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
fix tsconfig alias cycle (#59232) ### What? fixes https://github.com/vercel/next.js/issues/59195 fixes PACK-450 ### Why? ### How? see https://github.com/vercel/turbo/pull/6687 ### Turbopack Changes * https://github.com/vercel/turbo/pull/6627 <!-- Tobias Koppers - fix stack trace of errors --> * https://github.com/vercel/turbo/pull/6646 <!-- OJ Kwon - fix(turbo-tasks-fs): support unicode segment for glob --> * https://github.com/vercel/turbo/pull/6672 <!-- OJ Kwon - fix(ecmascript): dbg assert for the globals --> * https://github.com/vercel/turbo/pull/6687 <!-- Tobias Koppers - fix tsconfig alias cycle -->
2023-12-04 10:50:15 +01:00
"test/e2e/react-dnd-compile/react-dnd-compile.test.ts": {
"passed": [
"react-dnd-compile should work",
"react-dnd-compile should work on react-dnd import page"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/reload-scroll-backforward-restoration/index.test.ts": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"reload-scroll-back-restoration should restore the scroll position on navigating back",
"reload-scroll-back-restoration should restore the scroll position on navigating forward"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/repeated-forward-slashes-error/repeated-forward-slashes-error.test.ts": {
"passed": [
"repeated-forward-slashes-error should log error when href has repeated forward-slashes"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/skip-trailing-slash-redirect/index.test.ts": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"skip-trailing-slash-redirect app dir - skip trailing slash redirect should navigate client side correctly",
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"skip-trailing-slash-redirect app dir - skip trailing slash redirect should not apply trailing slash redirect (with slash)",
"skip-trailing-slash-redirect app dir - skip trailing slash redirect should not apply trailing slash redirect (without slash)",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"skip-trailing-slash-redirect app dir - skip trailing slash redirect should preserve original trailing slashes to links on client",
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"skip-trailing-slash-redirect app dir - skip trailing slash redirect should respond to dynamic route correctly",
"skip-trailing-slash-redirect app dir - skip trailing slash redirect should respond to index correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"skip-trailing-slash-redirect pages dir should navigate client side correctly",
"skip-trailing-slash-redirect pages dir should not apply trailing slash redirect (with slash)",
"skip-trailing-slash-redirect pages dir should not apply trailing slash redirect (without slash)",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"skip-trailing-slash-redirect pages dir should preserve original trailing slashes to links on client",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"skip-trailing-slash-redirect pages dir should respond to dynamic route correctly",
"skip-trailing-slash-redirect pages dir should respond to index correctly",
"skip-trailing-slash-redirect should allow response body from middleware with flag",
"skip-trailing-slash-redirect should allow rewriting invalid buildId correctly",
"skip-trailing-slash-redirect should apply config redirect correctly",
"skip-trailing-slash-redirect should apply config rewrites correctly",
"skip-trailing-slash-redirect should be able to redirect locale casing $1",
"skip-trailing-slash-redirect should correct skip URL normalizing in middleware",
"skip-trailing-slash-redirect should handle external rewrite correctly /chained-rewrite-ssg",
"skip-trailing-slash-redirect should handle external rewrite correctly /chained-rewrite-ssr",
"skip-trailing-slash-redirect should handle external rewrite correctly /chained-rewrite-static",
"skip-trailing-slash-redirect should handle external rewrite correctly /docs-auto-static/first",
"skip-trailing-slash-redirect should handle external rewrite correctly /docs-ssr/first",
"skip-trailing-slash-redirect should handle external rewrite correctly /docs/first",
"skip-trailing-slash-redirect should merge cookies from middleware and API routes correctly",
"skip-trailing-slash-redirect should merge cookies from middleware and edge API routes correctly",
"skip-trailing-slash-redirect should not apply trailing slash on load on client",
"skip-trailing-slash-redirect should parse locale info for data request correctly",
"skip-trailing-slash-redirect should provide original _next/data URL with skipMiddlewareUrlNormalize"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"test/e2e/socket-io/index.test.js": {
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"passed": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"socket-io should support socket.io without falling back to polling"
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/ssr-react-context/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"React Context should render a page with context",
"React Context should render correctly with context consumer",
"React Context should render with context after change"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/streaming-ssr/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"streaming SSR with custom next configs should match more specific route along with dynamic routes",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"streaming SSR with custom next configs should redirect paths without trailing-slash and render when slash is appended",
"streaming SSR with custom next configs should render multi-byte characters correctly in streaming",
"streaming SSR with custom next configs should render next/router correctly in edge runtime",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"streaming SSR with custom next configs should render styled-jsx styles in streaming",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"streaming SSR with custom next configs should work with custom document"
],
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/styled-jsx/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"styled-jsx should contain styled-jsx styles during SSR",
"styled-jsx should render styles during CSR",
"styled-jsx should render styles during CSR (AMP)",
"styled-jsx should render styles during SSR (AMP)"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/swc-warnings/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"failed": ["can force swc should not have warning"],
"pending": ["swc warnings by default should have warning"],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/switchable-runtime/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"Switchable runtime Switchable runtime (dev) should be able to navigate between edge SSR routes without any errors",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Switchable runtime Switchable runtime (dev) should be possible to switch between runtimes in API routes",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"Switchable runtime Switchable runtime (dev) should be possible to switch between runtimes in pages",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Switchable runtime Switchable runtime (dev) should not consume server.js file extension",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"Switchable runtime Switchable runtime (dev) should not include edge api routes and edge ssr routes into dev middleware manifest",
"Switchable runtime Switchable runtime (dev) should sort edge SSR routes correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"Switchable runtime Switchable runtime (dev) should build /api/hello and /api/edge as an api route with edge runtime"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
"pending": [
"Switchable runtime Switchable runtime (dev) should be possible to switch between runtimes with same content",
"Switchable runtime Switchable runtime (dev) should give proper errors for invalid runtime in app dir",
"Switchable runtime Switchable runtime (dev) should not crash the dev server when invalid runtime is configured",
"Switchable runtime Switchable runtime (dev) should recover from syntax error when using edge runtime",
"Switchable runtime Switchable runtime (dev) should support client side navigation to ssg rsc pages",
"Switchable runtime Switchable runtime (dev) should support client side navigation to ssr rsc pages",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Switchable runtime Switchable runtime (dev) should support client side navigation to static rsc pages"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/test-template/{{ toFileName name }}/{{ toFileName name }}.test.ts": {
"passed": [
"{{name}} should work using browser",
"{{name}} should work using cheerio",
"{{name}} should work with fetch",
"{{name}} should work with html"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/test-utils-tests/basic/basic.test.ts": {
"passed": ["createNextDescribe should work"],
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"test/e2e/testmode/testmode.test.ts": {
"passed": [
"testmode app router should handle API with fetch in edge function",
"testmode app router should handle API with fetch in serverless function",
"testmode app router should handle API with http.get in serverless function",
"testmode app router should handle RSC with fetch in edge function",
"testmode app router should handle RSC with fetch in serverless function",
"testmode app router should handle RSC with http.get in serverless function",
"testmode middleware should intercept fetchs in middleware",
"testmode page router should handle API with fetch",
"testmode page router should handle API with http.get",
"testmode page router should handle getServerSideProps with fetch",
"testmode page router should handle getServerSideProps with http.get",
"testmode rewrites should handle rewrites"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/third-parties/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"@next/third-parties basic usage renders GA",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"@next/third-parties basic usage renders GTM",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"@next/third-parties basic usage renders GoogleMapsEmbed",
"@next/third-parties basic usage renders YoutubeEmbed"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/trailingslash-with-rewrite/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"trailingSlash:true with rewrites and getStaticProps should work"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/transpile-packages/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"transpile packages css should handle css modules imports inside transpiled modules",
"transpile packages css should handle global css imports inside transpiled modules",
"transpile packages css should handle global scss imports inside transpiled modules",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"transpile packages css should handle scss modules imports inside transpiled modules",
"transpile packages optional deps should hide dynammic module dependency errors from node_modules",
"transpile packages optional deps should not throw an error when optional deps are not installed"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/type-module-interop/index.test.ts": {
"passed": [
"Type module interop should render client-side",
"Type module interop should render client-side with modules",
"Type module interop should render server-side",
"Type module interop should render server-side with modules"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/typescript-version-no-warning/typescript-version-no-warning.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": ["typescript-version-no-warning should skip"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/typescript-version-warning/typescript-version-warning.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": ["typescript-version-warning should skip"],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/undici-fetch/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"undici fetch undici global Headers should return true when undici is used",
"undici fetch undici global Request should return true when undici is used",
"undici fetch undici global Response should return true when undici is used",
"undici fetch undici global fetch should return true when undici is used"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/yarn-pnp/test/with-eslint.test.ts": {
"passed": [],
"failed": [
"yarn PnP should compile and serve the index page correctly with-eslint"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/yarn-pnp/test/with-mdx.test.ts": {
"passed": [],
"failed": [
"yarn PnP should compile and serve the index page correctly with-mdx"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/e2e/yarn-pnp/test/with-next-sass.test.ts": {
"passed": [],
"failed": [
"yarn PnP should compile and serve the index page correctly with-next-sass"
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/404-page-app/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"404 Page Support with _app dev mode should not show pages/404 GIP error if _app has GIP"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"404 Page Support with _app production mode should build successfully",
"404 Page Support with _app production mode should not output static 404 if _app has getInitialProps",
"404 Page Support with _app production mode should still use 404 page",
"404 Page Support with _app production mode specify to use the 404 page still in the routes-manifest"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/404-page-custom-error/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Default 404 Page with custom _error dev mode should render error correctly",
"Default 404 Page with custom _error dev mode should render index page normal",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Default 404 Page with custom _error dev mode should respond to 404 correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"Default 404 Page with custom _error production mode should build successfully",
"Default 404 Page with custom _error production mode should have output 404.html",
"Default 404 Page with custom _error production mode should render error correctly",
"Default 404 Page with custom _error production mode should render index page normal",
"Default 404 Page with custom _error production mode should respond to 404 correctly",
"Default 404 Page with custom _error production mode should set pages404 in routes-manifest correctly"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/404-page-ssg/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"404 Page Support SSG dev mode should not show an error in the logs for 404 SSG",
"404 Page Support SSG dev mode should render error correctly",
"404 Page Support SSG dev mode should render index page normal",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"404 Page Support SSG dev mode should respond to 404 correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"404 Page Support SSG production mode should build successfully",
"404 Page Support SSG production mode should have 404 page in prerender-manifest",
"404 Page Support SSG production mode should not revalidate custom 404 page",
"404 Page Support SSG production mode should not show an error in the logs for 404 SSG",
"404 Page Support SSG production mode should render error correctly",
"404 Page Support SSG production mode should render index page normal",
"404 Page Support SSG production mode should respond to 404 correctly",
"404 Page Support SSG production mode should set pages404 in routes-manifest correctly"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/404-page/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"404 Page Support dev mode 2 does not show error with getStaticProps in pages/404 dev",
"404 Page Support dev mode 2 falls back to _error correctly without pages/404",
"404 Page Support dev mode 2 shows error with getInitialProps in pages/404 dev",
"404 Page Support dev mode 2 shows error with getServerSideProps in pages/404 dev",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"404 Page Support dev mode should not error when visited directly",
"404 Page Support dev mode should render _error for a 500 error still",
"404 Page Support dev mode should set correct status code with pages/404",
"404 Page Support dev mode should use pages/404",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"404 Page Support dev mode should use pages/404 for .d.ts file"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"404 Page Support production mode does not show error with getStaticProps in pages/404 build",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"404 Page Support production mode should add /404 to pages-manifest correctly",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"404 Page Support production mode should not cache for custom 404 page with gssp and revalidate disabled",
"404 Page Support production mode should not cache for custom 404 page with gssp and revalidate enabled",
"404 Page Support production mode should not cache for custom 404 page without gssp",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"404 Page Support production mode should not error when visited directly",
"404 Page Support production mode should output 404.html during build",
"404 Page Support production mode should render _error for a 500 error still",
"404 Page Support production mode should set correct status code with pages/404",
"404 Page Support production mode should use pages/404",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"404 Page Support production mode should use pages/404 for .d.ts file",
"404 Page Support production mode shows error with getInitialProps in pages/404 build",
"404 Page Support production mode shows error with getServerSideProps in pages/404 build"
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/500-page/test/gsp-gssp.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"gsp-gssp development mode does not show error with getStaticProps in pages/500 dev",
"gsp-gssp development mode shows error with getServerSideProps in pages/500 dev"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"gsp-gssp production mode does build 500 statically with getInitialProps in _app and getStaticProps in pages/500",
"gsp-gssp production mode does not build 500 statically with no pages/500 and getServerSideProps in _error",
"gsp-gssp production mode does not show error with getStaticProps in pages/500 build",
"gsp-gssp production mode shows error with getServerSideProps in pages/500 build"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/500-page/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"500 Page Support dev mode should not error when visited directly",
"500 Page Support dev mode should set correct status code with pages/500",
"500 Page Support dev mode should use pages/500",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"500 Page Support development mode 2 shows error with getInitialProps in pages/500 dev"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"500 Page Support production mode 2 builds 500 statically by default with no pages/500",
"500 Page Support production mode 2 builds 500 statically by default with no pages/500 and custom _error without getInitialProps",
"500 Page Support production mode 2 does not build 500 statically with getInitialProps in _app",
"500 Page Support production mode 2 does not build 500 statically with no pages/500 and custom getInitialProps in _error",
"500 Page Support production mode 2 does not build 500 statically with no pages/500 and custom getInitialProps in _error and _app",
"500 Page Support production mode 2 shows error with getInitialProps in pages/500 build",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"500 Page Support production mode should add /500 to pages-manifest correctly",
"500 Page Support production mode should not error when visited directly",
"500 Page Support production mode should output 500.html during build",
"500 Page Support production mode should set correct status code with pages/500",
"500 Page Support production mode should use pages/500"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
"runtimeError": false
},
"test/integration/absolute-assetprefix/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"absolute assetPrefix with path prefix production mode should fetch from cache correctly",
"absolute assetPrefix with path prefix production mode should not fetch static data from a CDN",
"absolute assetPrefix with path prefix production mode should work with getServerSideProps",
"absolute assetPrefix with path prefix production mode should work with getStaticPaths fallback",
"absolute assetPrefix with path prefix production mode should work with getStaticPaths prerendered"
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/amp-export-validation/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"AMP Validation on Export production mode should have shown errors during build",
"AMP Validation on Export production mode shows AMP warning without throwing error",
"AMP Validation on Export production mode shows warning and error when throwing error",
"AMP Validation on Export production mode throws error on AMP error"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/amphtml-custom-optimizer/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"AMP Custom Optimizer production mode should build and start for dynamic page",
"AMP Custom Optimizer production mode should build and start for static page"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/amphtml-custom-validator/test/index.test.js": {
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"passed": [],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"AMP Custom Validator development mode should run in dev mode successfully",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"AMP Custom Validator production mode should build and start successfully"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/amphtml-fragment-style/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"AMP Fragment Styles production mode adds styles from fragment in AMP mode correctly"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/amphtml-ssg/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"AMP SSG Support dev mode should load a hybrid amp page with query correctly",
"AMP SSG Support dev mode should load a hybrid amp page without query correctly",
"AMP SSG Support dev mode should load an amp first page correctly",
"AMP SSG Support dev mode should load dynamic hybrid SSG/AMP page",
"AMP SSG Support dev mode should load dynamic hybrid SSG/AMP page with query",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"AMP SSG Support dev mode should load dynamic hybrid SSG/AMP page with trailing slash"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"AMP SSG Support export mode production mode should have copied SSG files correctly",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"AMP SSG Support production mode should load a hybrid amp page with query correctly",
"AMP SSG Support production mode should load a hybrid amp page without query correctly",
"AMP SSG Support production mode should load an amp first page correctly",
"AMP SSG Support production mode should load dynamic hybrid SSG/AMP page",
"AMP SSG Support production mode should load dynamic hybrid SSG/AMP page with query",
"AMP SSG Support production mode should load dynamic hybrid SSG/AMP page with trailing slash",
"AMP SSG Support production mode should output prerendered files correctly during build"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/amphtml/test/index.test.js": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"AMP Usage AMP dev mode should detect amp validator warning on invalid amp",
"AMP Usage AMP dev mode should navigate from non-AMP to AMP without error",
"AMP Usage AMP dev mode should not contain missing files warning",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"AMP Usage AMP dev no-warn should not warn on valid amp"
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [
"AMP Usage AMP dev mode should add data-ampdevmode to development script tags"
],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"AMP Usage AMP dev mode should detect changes and refresh a hybrid AMP page",
"AMP Usage AMP dev mode should detect changes and refresh an AMP page",
"AMP Usage AMP dev mode should detect changes and refresh an AMP page at root pages/",
"AMP Usage AMP dev mode should detect changes to component and refresh an AMP page",
"AMP Usage AMP dev mode should detect the changes and display it",
"AMP Usage AMP dev mode should not reload unless the page is edited for an AMP page",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"AMP Usage production mode With AMP context should render nested AMP page with AMP hook",
"AMP Usage production mode With AMP context should render nested normal page with AMP hook",
"AMP Usage production mode With AMP context should render the AMP page that uses the AMP hook",
"AMP Usage production mode With AMP context should render the normal page that uses the AMP hook",
"AMP Usage production mode With basic AMP usage should auto import extensions",
"AMP Usage production mode With basic AMP usage should drop custom scripts",
"AMP Usage production mode With basic AMP usage should not drop custom amp scripts",
"AMP Usage production mode With basic AMP usage should not output client pages for AMP only",
"AMP Usage production mode With basic AMP usage should not output client pages for AMP only with config exported after declaration",
"AMP Usage production mode With basic AMP usage should optimize clean",
"AMP Usage production mode With basic AMP usage should render the page as valid AMP",
"AMP Usage production mode With basic AMP usage should render the page without leaving render target",
"AMP Usage production mode With basic usage should render the page",
"AMP Usage production mode canonical amphtml should allow manually setting amphtml rel",
"AMP Usage production mode canonical amphtml should allow manually setting canonical",
"AMP Usage production mode canonical amphtml should not render amphtml link tag with no AMP page",
"AMP Usage production mode canonical amphtml should remove conflicting amp tags",
"AMP Usage production mode canonical amphtml should render a canonical regardless of amp-only status (explicit)",
"AMP Usage production mode canonical amphtml should render amphtml from provided rel link",
"AMP Usage production mode canonical amphtml should render link rel amphtml",
"AMP Usage production mode canonical amphtml should render link rel amphtml with existing query",
"AMP Usage production mode canonical amphtml should render the AMP page that uses the AMP hook",
"AMP Usage production mode combined styles should combine style tags",
"AMP Usage production mode combined styles should remove sourceMaps from styles",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"AMP Usage production mode should have amp optimizer in trace",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"AMP Usage production mode should not contain missing files warning"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/api-body-parser/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"should not throw if request body is already parsed in custom middleware",
"should not throw if request's content-type is invalid",
"should parse JSON body"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/api-catch-all/test/index.test.js": {
"passed": [
"API routes dev support should return data when catch-all",
"API routes dev support should return data when catch-all with index and no trailing slash",
"API routes dev support should return data when catch-all with index and trailing slash",
"API routes dev support should return redirect when catch-all with index and trailing slash"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"API routes production mode should return data when catch-all",
"API routes production mode should return data when catch-all with index and no trailing slash",
"API routes production mode should return data when catch-all with index and trailing slash",
"API routes production mode should return redirect when catch-all with index and trailing slash"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/api-support/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"API routes dev support should 404 on optional dynamic api page",
"API routes dev support should compile only server code in development",
"API routes dev support should handle 204 status correctly",
"API routes dev support should handle proxying to self correctly",
"API routes dev support should not conflict with /api routes",
"API routes dev support should not show warning if using externalResolver flag",
"API routes dev support should not show warning when the API resolves and the response is piped",
"API routes dev support should not warn if response body is larger than 4MB with responseLimit config = false",
"API routes dev support should parse JSON body",
"API routes dev support should parse bigger body then 1mb",
"API routes dev support should parse body in handler",
"API routes dev support should parse body with config",
"API routes dev support should parse query correctly",
"API routes dev support should parse urlencoded body",
"API routes dev support should prioritize a non-dynamic page",
"API routes dev support should redirect to login",
"API routes dev support should redirect with status code 301",
"API routes dev support should redirect with status code 307",
"API routes dev support should render page",
"API routes dev support should respond from /api/auth/[...nextauth] correctly",
"API routes dev support should return 200 on POST on pages",
"API routes dev support should return 404 for undefined path",
"API routes dev support should return JSON on post on API",
"API routes dev support should return cookies object",
"API routes dev support should return custom error",
"API routes dev support should return data on dynamic nested route",
"API routes dev support should return data on dynamic optional nested route",
"API routes dev support should return data on dynamic route",
"API routes dev support should return empty cookies object",
"API routes dev support should return empty query object",
"API routes dev support should return error with invalid JSON",
"API routes dev support should set cors headers when adding cors middleware",
"API routes dev support should show false positive warning if not using externalResolver flag",
"API routes dev support should show friendly error for invalid redirect",
"API routes dev support should show friendly error in case of passing null as first argument redirect",
"API routes dev support should show warning when the API resolves without ending the request in dev mode",
"API routes dev support should special-case empty JSON body",
"API routes dev support should support boolean for JSON in api page",
"API routes dev support should support etag spec",
"API routes dev support should support null in JSON response body",
"API routes dev support should support string in JSON response body",
"API routes dev support should support undefined response body",
"API routes dev support should throw Internal Server Error",
"API routes dev support should throw Internal Server Error (async)",
"API routes dev support should warn if response body is larger than 4MB",
"API routes dev support should warn with configured size if response body is larger than configured size",
"API routes dev support should work with child_process correctly",
"API routes dev support should work with dynamic params and search string",
"API routes dev support should work with dynamic params and search string like lambda",
"API routes dev support should work with index api",
"API routes dev support should work with nullable payload"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"API routes dev support should return error exceeded body limit",
"API routes production mode should 404 on optional dynamic api page",
"API routes production mode should build api routes",
"API routes production mode should handle 204 status correctly",
"API routes production mode should handle proxying to self correctly",
"API routes production mode should not conflict with /api routes",
"API routes production mode should not warn if response body is larger than 4MB with responseLimit config = false",
"API routes production mode should parse JSON body",
"API routes production mode should parse bigger body then 1mb",
"API routes production mode should parse body in handler",
"API routes production mode should parse body with config",
"API routes production mode should parse query correctly",
"API routes production mode should parse urlencoded body",
"API routes production mode should prioritize a non-dynamic page",
"API routes production mode should redirect to login",
"API routes production mode should redirect with status code 301",
"API routes production mode should redirect with status code 307",
"API routes production mode should render page",
"API routes production mode should respond from /api/auth/[...nextauth] correctly",
"API routes production mode should return 200 on POST on pages",
"API routes production mode should return 404 for undefined path",
"API routes production mode should return JSON on post on API",
"API routes production mode should return cookies object",
"API routes production mode should return custom error",
"API routes production mode should return data on dynamic nested route",
"API routes production mode should return data on dynamic optional nested route",
"API routes production mode should return data on dynamic route",
"API routes production mode should return empty cookies object",
"API routes production mode should return empty query object",
"API routes production mode should return error exceeded body limit",
"API routes production mode should return error with invalid JSON",
"API routes production mode should set cors headers when adding cors middleware",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"API routes production mode should show error with output export",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"API routes production mode should show friendly error for invalid redirect",
"API routes production mode should show friendly error in case of passing null as first argument redirect",
"API routes production mode should special-case empty JSON body",
"API routes production mode should support boolean for JSON in api page",
"API routes production mode should support etag spec",
"API routes production mode should support null in JSON response body",
"API routes production mode should support string in JSON response body",
"API routes production mode should support undefined response body",
"API routes production mode should throw Internal Server Error",
"API routes production mode should throw Internal Server Error (async)",
"API routes production mode should warn if response body is larger than 4MB",
"API routes production mode should warn with configured size if response body is larger than configured size",
"API routes production mode should work with child_process correctly",
"API routes production mode should work with dynamic params and search string",
"API routes production mode should work with dynamic params and search string like lambda",
"API routes production mode should work with index api",
"API routes production mode should work with nullable payload"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-aspath/test/index.test.js": {
"passed": [
"App asPath should not have any changes in asPath after a bundle rebuild"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-config-asset-prefix/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"App assetPrefix config should render correctly with assetPrefix: \"/\""
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-dir-export/test/config.test.ts": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - with output export (next dev / next build) production mode should correctly emit exported assets to config.distDir",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - with output export (next dev / next build) production mode should error when running next export",
"app dir - with output export (next dev / next build) production mode should throw when exportPathMap configured"
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-dir-export/test/dynamic-missing-gsp-dev.test.ts": {
fix(next-core): do not panic when parsing segment config (#59170)
2023-12-01 21:54:01 +01:00
"passed": [
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"app dir - with output export - dynamic missing gsp dev development mode should error when dynamic route is missing generateStaticParams",
"app dir - with output export - dynamic missing gsp dev development mode should error when generateStaticParams returns an empty array"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
fix(next-core): do not panic when parsing segment config (#59170)
2023-12-01 21:54:01 +01:00
"failed": [
"app dir - with output export - dynamic missing gsp dev development mode should error when client component has generateStaticParams"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-dir-export/test/dynamic-missing-gsp-prod.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"failed": [],
"pending": [
"app dir - with output export - dynamic missing gsp prod production mode should error when client component has generateStaticParams",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"app dir - with output export - dynamic missing gsp prod production mode should error when dynamic route is missing generateStaticParams",
"app dir - with output export - dynamic missing gsp prod production mode should error when generateStaticParams returns an empty array"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-dir-export/test/dynamicapiroute-dev.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
"failed": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - with output export - dynamic api route dev development mode should work in dev with dynamicApiRoute 'error'",
"app dir - with output export - dynamic api route dev development mode should work in dev with dynamicApiRoute 'force-dynamic'",
"app dir - with output export - dynamic api route dev development mode should work in dev with dynamicApiRoute 'force-static'",
"app dir - with output export - dynamic api route dev development mode should work in dev with dynamicApiRoute undefined"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-dir-export/test/dynamicapiroute-prod.test.ts": {
"passed": [],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"failed": [],
"pending": [
"app dir - with output export - dynamic api route prod production mode should work in prod with dynamicApiRoute 'error'",
"app dir - with output export - dynamic api route prod production mode should work in prod with dynamicApiRoute 'force-dynamic'",
"app dir - with output export - dynamic api route prod production mode should work in prod with dynamicApiRoute 'force-static'",
"app dir - with output export - dynamic api route prod production mode should work in prod with dynamicApiRoute undefined"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-dir-export/test/dynamicpage-dev.test.ts": {
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"passed": [
"app dir - with output export - dynamic page dev development mode should work in dev with dynamicPage 'force-dynamic'"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - with output export - dynamic page dev development mode should work in dev with dynamicPage 'error'",
"app dir - with output export - dynamic page dev development mode should work in dev with dynamicPage 'force-static'",
"app dir - with output export - dynamic page dev development mode should work in dev with dynamicPage undefined"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-dir-export/test/dynamicpage-prod.test.ts": {
Fix mjs import for Turbopack test (#56354) Turbopack currently supports fully-specified `.mjs` imports. Double check with @sokra to verify if this is correct. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-10-03 13:33:04 +02:00
"passed": [],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"failed": [],
"pending": [
"app dir - with output export - dynamic api route prod production mode should work in prod with dynamicPage $dynamicPage",
"app dir - with output export - dynamic api route prod production mode should work in prod with dynamicPage 'force-dynamic'",
"app dir - with output export - dynamic api route prod production mode should work in prod with dynamicPage 'force-static'",
"app dir - with output export - dynamic api route prod production mode should work in prod with dynamicPage undefined"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-dir-export/test/start.test.ts": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"app dir - with output export (next start) production mode should error during next start with output export",
"app dir - with output export (next start) production mode should warn during next start with output standalone"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-dir-export/test/trailing-slash-dev.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
"failed": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"app dir - with output export - trailing slash dev development mode should work in dev with trailingSlash 'false'",
"app dir - with output export - trailing slash dev development mode should work in dev with trailingSlash 'true'"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-dir-export/test/trailing-slash-start.test.ts": {
"passed": [],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"failed": [],
"pending": [
"app dir - with output export - trailing slash prod production mode should work in prod with trailingSlash 'false'",
"app dir - with output export - trailing slash prod production mode should work in prod with trailingSlash 'true'"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/app-document-add-hmr/test/index.test.js": {
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [
"_app/_document add HMR should HMR when _app is added",
"_app/_document add HMR should HMR when _document is added"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/app-document-import-order/test/index.test.js": {
"passed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"development mode root components should be imported in this order _document > _app > page in order to respect side effects"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
"failed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"development mode _app chunks should be attached to de dom before page chunks"
],
"pending": [
"Root components import order production mode _app chunks should be attached to de dom before page chunks",
"Root components import order production mode root components should be imported in this order _document > _app > page in order to respect side effects"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-document-remove-hmr/test/index.test.js": {
add flakey test (#56080) It's flakey for turbopack Closes WEB-1671 Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-09-27 13:24:35 +02:00
"passed": ["_app removal HMR should HMR when _app is removed"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
add flakey test (#56080) It's flakey for turbopack Closes WEB-1671 Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-09-27 13:24:35 +02:00
"flakey": ["_app removal HMR should HMR when _document is removed"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-document-style-fragment/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Custom Document Fragment Styles production mode correctly adds styles from fragment styles key"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-document/test/index.test.js": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Document and App Client side It should share module state with pages",
"Document and App Client side should keep state between page navigations",
"Document and App Rendering via HTTP _app It should share module state with pages",
"Document and App Rendering via HTTP _app It should show valid error when thrown in _app getInitialProps",
"Document and App Rendering via HTTP _app It shows a custom tag",
"Document and App Rendering via HTTP _document Document.getInitialProps returns html prop representing app shell",
"Document and App Rendering via HTTP _document It adds a timestamp to link tags with preload attribute to invalidate the cache (DEV only)",
"Document and App Rendering via HTTP _document It adds crossOrigin to all scripts and preload links",
"Document and App Rendering via HTTP _document It adds nonces to all scripts and preload links",
"Document and App Rendering via HTTP _document It renders ctx.renderPage with enhanceApp and enhanceComponent correctly",
"Document and App Rendering via HTTP _document It renders ctx.renderPage with enhanceApp correctly",
"Document and App Rendering via HTTP _document It renders ctx.renderPage with enhanceComponent correctly",
"Document and App Rendering via HTTP _document It renders ctx.renderPage with enhancer correctly",
"Document and App Rendering via HTTP _document should include required elements in rendered html",
"Document and App With CSP enabled should load inline script by hash",
"Document and App With CSP enabled should load inline script by nonce",
"Document and App should not have any missing key warnings"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [],
"flakey": [
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"Document and App Client side should detect the changes to pages/_app.js and display it",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Document and App Client side should detect the changes to pages/_document.js and display it"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-dynamic-error/test/index.test.ts": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"app-dynamic-error production mode throws an error when prerendering a page with config dynamic error"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-functional/test/index.test.js": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": ["Document and App should not have any missing key warnings"],
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-tree/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"AppTree dev mode should pass AppTree to NextPageContext",
"AppTree dev mode should provide router context in AppTree on CSR",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"AppTree dev mode should provide router context in AppTree on SSR"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"AppTree production mode should pass AppTree to NextPageContext",
"AppTree production mode should provide router context in AppTree on CSR",
"AppTree production mode should provide router context in AppTree on SSR"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/app-types/app-types.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"app type checking production mode should generate route types correctly and report link error",
"app type checking production mode should generate route types correctly and report router API errors",
"app type checking production mode should type check invalid entry exports"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/async-modules/test/index.test.js": {
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Async modules dev mode can render async 404 pages",
"Async modules dev mode csr async page modules",
"Async modules dev mode ssr async page modules",
"Async modules dev mode works on async api routes",
"Async modules dev mode works with getServerSideProps",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Async modules dev mode works with getStaticProps"
],
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"Async modules dev mode can render async AMP pages",
"Async modules dev mode can render async error page",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Async modules production mode can render async 404 pages",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Async modules production mode can render async AMP pages",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Async modules production mode can render async error page",
"Async modules production mode csr async page modules",
"Async modules production mode ssr async page modules",
"Async modules production mode works on async api routes",
"Async modules production mode works with getServerSideProps",
"Async modules production mode works with getStaticProps"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/auto-export-error-bail/test/index.test.js": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"Auto Export _error bail production mode should not opt-out of auto static optimization from invalid _error"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/auto-export-query-error/test/index.test.js": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"Auto Export production mode should show warning for query provided for auto exported page correctly"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/auto-export/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Auto Export dev Refreshes query on mount",
"Auto Export dev Supports commonjs 1",
"Auto Export dev Supports commonjs 2",
"Auto Export dev should include error link when hydration error does occur",
"Auto Export dev should not replace URL with page name while asPath is delayed",
"Auto Export dev should not show hydration warning from mismatching asPath",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Auto Export dev should update asPath after mount"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Auto Export production mode Refreshes query on mount",
"Auto Export production mode Supports commonjs 1",
"Auto Export production mode Supports commonjs 2",
"Auto Export production mode should not replace URL with page name while asPath is delayed",
"Auto Export production mode should update asPath after mount"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/babel-custom/test/index.test.js": {
"passed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Babel should allow babelrc JSON5 syntax",
"Babel should allow setting babelrc env",
"Babel should allow setting targets to a string",
"Babel should allow setting targets.browsers"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/babel/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Babel Rendering via HTTP Should compile a page with flowtype correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/basepath-root-catch-all/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"dev mode should use correct data URL for root catch-all",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"production mode should use correct data URL for root catch-all"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/bigint/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"bigint API route support dev mode should return 200",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"bigint API route support dev mode should return the BigInt result text"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"bigint API route support production mode should return 200",
"bigint API route support production mode should return the BigInt result text"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/broken-webpack-plugin/test/index.test.js": {
"passed": [],
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Handles a broken webpack plugin (precompile) should render error correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/build-indicator/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Build Activity Indicator Disabled with next.config.js Does not add the build indicator container",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Build Activity Indicator Enabled Adds the build indicator container",
"Build Activity Indicator Enabled Shows build indicator when page is built from modifying",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Build Activity Indicator should validate buildActivityPosition config"
],
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"failed": [],
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"pending": [
"Build Activity Indicator Enabled webpack only Shows the build indicator when a page is built during navigation"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/build-output/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Build Output production mode Basic Application Output (experimental: {\"gzipSize\":false}) should not deviate from snapshot",
"Build Output production mode Basic Application Output (experimental: {\"gzipSize\":false}) should not emit extracted comments",
"Build Output production mode Basic Application Output (experimental: {\"gzipSize\":false}) should not include internal pages",
"Build Output production mode Basic Application Output (experimental: {\"gzipSize\":false}) should print duration when rendering or get static props takes long",
"Build Output production mode Basic Application Output (experimental: {}) should not deviate from snapshot",
"Build Output production mode Basic Application Output (experimental: {}) should not emit extracted comments",
"Build Output production mode Basic Application Output (experimental: {}) should not include internal pages",
"Build Output production mode Basic Application Output (experimental: {}) should print duration when rendering or get static props takes long",
"Build Output production mode Custom App Output should not include custom error",
"Build Output production mode Custom Error Output should not include custom app",
"Build Output production mode Custom Static Error Output should not specify /404 as lambda when static",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"Build Output production mode With AMP Output should not include custom error",
"Build Output production mode With Parallel Routes should not have duplicate paths that resolve to the same route"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/build-trace-extra-entries-turbo/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"build trace with extra entries production mode should build and trace correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/build-trace-extra-entries/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"build trace with extra entries production mode should build and trace correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/build-warnings/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"Build warnings production mode should not shown warning about minification without any modification",
"Build warnings production mode should not warn about missing cache in non-CI",
"Build warnings production mode should not warn about missing cache on supported platforms",
"Build warnings production mode should shown warning about minification for minimize",
"Build warnings production mode should shown warning about minification for minimizer",
"Build warnings production mode should warn about missing cache in CI"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/catches-missing-getStaticProps/test/index.test.js": {
"passed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Catches Missing getStaticProps development mode should catch it in dev mode"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Catches Missing getStaticProps production mode should catch it in server build mode"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/chunking/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
"pending": [
"Chunking production mode Serving should hydrate with aggressive chunking",
"Chunking production mode Serving should load chunks when navigating",
"Chunking production mode should create a framework chunk",
"Chunking production mode should execute the build manifest",
"Chunking production mode should not create a commons chunk",
"Chunking production mode should not create a lib chunk for react or react-dom",
"Chunking production mode should not include more than one instance of react-dom",
"Chunking production mode should not preload the build manifest",
"Chunking production mode should use all url friendly names"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/clean-distdir/test/index.test.js": {
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"Cleaning distDir production mode disabled write should not clean up .next before build start",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Cleaning distDir production mode should clean up .next before build start"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/cli/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"CLI Usage dev --experimental-https",
"CLI Usage dev --experimental-https with provided key/cert",
"CLI Usage dev --help",
"CLI Usage dev --hostname",
"CLI Usage dev --port",
"CLI Usage dev --port 0",
"CLI Usage dev -H",
"CLI Usage dev -h",
"CLI Usage dev -p",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"CLI Usage dev -p conflict",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"CLI Usage dev -p reserved",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"CLI Usage dev NODE_OPTIONS='--inspect'",
"CLI Usage dev PORT=0",
"CLI Usage dev custom directory",
"CLI Usage dev invalid directory",
"CLI Usage dev should exit when SIGINT is signalled",
"CLI Usage dev should exit when SIGTERM is signalled",
"CLI Usage dev should format IPv6 addresses correctly",
"CLI Usage dev should not throw UnhandledPromiseRejectionWarning",
"CLI Usage dev should warn when unknown argument provided",
"CLI Usage export --help",
"CLI Usage info --help",
"CLI Usage info -h",
"CLI Usage info should print output",
"CLI Usage info should print output with next.config.mjs",
"CLI Usage no command --help",
"CLI Usage no command --version",
"CLI Usage no command -h",
"CLI Usage no command -v",
"CLI Usage no command detects command typos",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"CLI Usage no command invalid directory"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"CLI Usage production mode build --help",
"CLI Usage production mode build -h",
"CLI Usage production mode build invalid directory",
"CLI Usage production mode build should exit when SIGINT is signalled",
"CLI Usage production mode build should exit when SIGTERM is signalled",
"CLI Usage production mode build should not throw UnhandledPromiseRejectionWarning",
"CLI Usage production mode build should warn when unknown argument provided",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"CLI Usage production mode start --help",
"CLI Usage production mode start --keepAliveTimeout Infinity",
"CLI Usage production mode start --keepAliveTimeout happy path",
"CLI Usage production mode start --keepAliveTimeout negative number",
"CLI Usage production mode start --keepAliveTimeout string arg",
"CLI Usage production mode start -h",
"CLI Usage production mode start duplicate sass deps",
"CLI Usage production mode start invalid directory",
"CLI Usage production mode start should exit when SIGINT is signalled",
"CLI Usage production mode start should exit when SIGTERM is signalled",
"CLI Usage production mode start should format IPv6 addresses correctly",
"CLI Usage production mode start should not start on a port out of range",
"CLI Usage production mode start should not start on a reserved port",
"CLI Usage production mode start should not throw UnhandledPromiseRejectionWarning",
"CLI Usage production mode start should warn when unknown argument provided",
"CLI Usage production mode telemetry --help",
"CLI Usage production mode telemetry -h",
"CLI Usage production mode telemetry should not throw UnhandledPromiseRejectionWarning",
"CLI Usage production mode telemetry should warn when unknown argument provided"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/client-404/test/index.test.js": {
"passed": [
"Client 404 dev mode Client Navigation 404 should hard navigate to URL on failing to load bundle",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Client 404 dev mode Client Navigation 404 should show 404 upon client replacestate should navigate the page"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Client 404 production mode Client Navigation 404 should hard navigate to URL on failing to load bundle",
"Client 404 production mode Client Navigation 404 should hard navigate to URL on failing to load missing bundle",
"Client 404 production mode Client Navigation 404 should show 404 upon client replacestate should navigate the page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/client-navigation-a11y/test/index.test.js": {
"passed": [
"Client Navigation accessibility <RouteAnnouncer /> There is a title and a h1 tag has the innerText equal to the value of h1",
"Client Navigation accessibility <RouteAnnouncer /> There is a title but no h1 tag has the innerText equal to the value of document.title",
"Client Navigation accessibility <RouteAnnouncer /> There is no title and no h1 tag has the innerText equal to the value of the pathname",
"Client Navigation accessibility <RouteAnnouncer /> There is no title but a h1 tag has the innerText equal to the value of h1",
"Client Navigation accessibility <RouteAnnouncer /> has aria-live=\"assertive\" and role=\"alert\"",
"Client Navigation accessibility <RouteAnnouncer /> should not have the initial route announced"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/client-shallow-routing/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Client Shallow Routing dev mode should not shallowly navigate back in history when current page was not shallow",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Client Shallow Routing dev mode should not shallowly navigate forwards in history when current page was not shallow"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Client Shallow Routing production mode should not shallowly navigate back in history when current page was not shallow",
"Client Shallow Routing production mode should not shallowly navigate forwards in history when current page was not shallow"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/compression/test/index.test.js": {
"passed": ["Compression should compress responses by default"],
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/config-devtool-dev/test/index.test.js": {
"passed": [],
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"devtool set in development mode in next config should warn and revert when a devtool is set in development mode"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/config-experimental-warning/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Config Experimental Warning should not show warning with config from object",
"Config Experimental Warning should not show warning with default config from function",
"Config Experimental Warning should not show warning with default value",
"Config Experimental Warning should show warning with config from function with experimental",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Config Experimental Warning should show warning with config from object with experimental",
"Config Experimental Warning should show warning with config from object with experimental and multiple keys"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"failed": [],
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"pending": [
"Config Experimental Warning production mode should not show next app info in next start",
"Config Experimental Warning production mode should show next app info with all experimental features in next build",
"Config Experimental Warning production mode should show unrecognized experimental features in warning but not in start log experiments section"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/config-mjs/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Configuration correctly imports a package that defines `module` but no `main` in package.json",
"Configuration renders public config on the server only",
"Configuration renders server config on the server only",
"Configuration should disable X-Powered-By header support",
"Configuration should have config available on the client"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/config-output-export/test/index.test.ts": {
"passed": [
"config-output-export should error with \"i18n\" config",
"config-output-export should error with api routes function",
"config-output-export should error with getServerSideProps without fallback",
"config-output-export should error with getStaticPaths and fallback blocking",
"config-output-export should error with getStaticPaths and fallback true",
"config-output-export should error with getStaticProps and revalidate 10 seconds (ISR)",
"config-output-export should error with middleware function",
"config-output-export should work with getStaticPaths and fallback false",
"config-output-export should work with getStaticProps and revalidate false",
"config-output-export should work with getStaticProps and without revalidate",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"config-output-export should work with static homepage",
"config-output-export when hasNextSupport = false should error with \"headers\" config",
"config-output-export when hasNextSupport = false should error with \"redirects\" config",
"config-output-export when hasNextSupport = false should error with \"rewrites\" config",
"config-output-export when hasNextSupport = true should error with \"headers\" config",
"config-output-export when hasNextSupport = true should error with \"redirects\" config",
"config-output-export when hasNextSupport = true should error with \"rewrites\" config"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/config-promise-error/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Promise in next config production mode should warn when a promise is returned on webpack"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/config-resolve-alias/test/index.test.js": {
"passed": [],
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Invalid resolve alias should show relevant error when webpack resolve alias is wrong"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/config-syntax-error/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Invalid config syntax production mode should error when next.config.js contains syntax error",
"Invalid config syntax production mode should error when next.config.mjs contains syntax error"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/config-validation/test/index.test.ts": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"next.config.js validation production mode it should validate correctly for invalid config types",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"next.config.js validation production mode it should validate correctly for unexpected config fields",
"next.config.js validation production mode should allow undefined environment variables"
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/config/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Configuration correctly imports a package that defines `module` but no `main` in package.json",
"Configuration renders public config on the server only",
"Configuration renders server config on the server only",
"Configuration should disable X-Powered-By header support",
"Configuration should have config available on the client"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/conflicting-public-file-page/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Errors on conflict between public file and page file development mode Throws error during development"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Errors on conflict between public file and page file production mode Throws error during build"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/conflicting-ssg-paths/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Conflicting SSG paths production mode should show proper error when a dynamic SSG route conflicts with SSR route",
"Conflicting SSG paths production mode should show proper error when a dynamic SSG route conflicts with normal route",
"Conflicting SSG paths production mode should show proper error when two dynamic SSG routes have conflicting paths"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/create-next-app/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"create next app empty directory",
"create next app invalid example name",
"create next app non-empty directory",
"create next app should allow an example named default",
"create next app should allow example with GitHub URL",
"create next app should allow example with GitHub URL and example-path",
"create next app should allow example with GitHub URL with trailing slash",
"create next app should ask the user for a name for the project if none supplied",
"create next app should create a project in the current directory",
"create next app should exit if example flag is empty",
"create next app should exit if the folder is not writable",
"create next app should fall back to default template",
"create next app should use --example-path over the file path in the GitHub URL",
"create next app valid example",
"create next app valid example without package.json"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/create-next-app/package-manager.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"should infer Bun as the package manager",
"should infer Bun as the package manager with example",
"should infer npm as the package manager",
"should infer npm as the package manager with example",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"should infer pnpm as the package manager",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"should infer pnpm as the package manager with example",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"should infer yarn as the package manager",
"should infer yarn as the package manager with example",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"should use Bun as the package manager on supplying --use-bun",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"should use Bun as the package manager on supplying --use-bun with example",
"should use Yarn as the package manager on supplying --use-yarn",
"should use Yarn as the package manager on supplying --use-yarn with example",
"should use npm as the package manager on supplying --use-npm",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"should use npm as the package manager on supplying --use-npm with example",
update manifest (#57421) update manifest from daily test run Closes WEB-1856
2023-10-25 16:41:30 +02:00
"should use pnpm as the package manager on supplying --use-pnpm",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"should use pnpm as the package manager on supplying --use-pnpm with example"
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"pending": [],
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/create-next-app/templates-app.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"create-next-app --app should create JS appDir projects with --js",
"create-next-app --app should create JS appDir projects with --js --src-dir",
"create-next-app --app should create TS appDir projects with --ts",
"create-next-app --app should create Tailwind CSS appDir projects with --tailwind"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/create-next-app/templates-pages.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"create-next-app templates should create JS projects with --js, --javascript",
"create-next-app templates should create JS projects with --js, --javascript --src-dir",
"create-next-app templates should create TS projects with --ts, --typescript",
"create-next-app templates should create TS projects with --ts, --typescript --src-dir",
"create-next-app templates should prompt user to choose if --import-alias is not provided",
"create-next-app templates should prompt user to choose if --tailwind or --no-tailwind is not provided",
"create-next-app templates should prompt user to choose if --ts or --js is not provided",
"create-next-app templates should work with --tailwind and --src together"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/critical-css/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"CSS optimization for SSR apps production mode should have all CSS files in manifest",
"CSS optimization for SSR apps production mode should inline critical CSS",
"CSS optimization for SSR apps production mode should inline critical CSS (dynamic)",
"CSS optimization for SSR apps production mode should not inline non-critical css"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/css-client-nav/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"CSS Module client-side navigation dev should be able to client-side navigate from blue to red",
"CSS Module client-side navigation dev should be able to client-side navigate from none to blue",
"CSS Module client-side navigation dev should be able to client-side navigate from none to red",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"CSS Module client-side navigation dev should be able to client-side navigate from red to blue"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"CSS Module client-side navigation production mode should be able to client-side navigate from blue to red",
"CSS Module client-side navigation production mode should be able to client-side navigate from none to blue",
"CSS Module client-side navigation production mode should be able to client-side navigate from none to red",
"CSS Module client-side navigation production mode should be able to client-side navigate from red to blue",
"CSS Module client-side navigation production mode should time out and hard navigate for stalled CSS request"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/css-customization/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
"pending": [
"CSS Customization production mode Bad CSS Customization Array (1) should fail the build",
"CSS Customization production mode Bad CSS Customization Array (2) should fail the build",
"CSS Customization production mode Bad CSS Customization Array (3) should fail the build",
"CSS Customization production mode Bad CSS Customization Array (4) should fail the build",
"CSS Customization production mode Bad CSS Customization Array (5) should fail the build",
"CSS Customization production mode Bad CSS Customization Array (6) should fail the build",
"CSS Customization production mode Bad CSS Customization Array (7) should fail the build",
"CSS Customization production mode Bad CSS Customization Array (8) should fail the build",
"CSS Customization production mode Bad CSS Customization Function should fail the build",
"CSS Customization production mode Bad CSS Customization should compile successfully",
"CSS Customization production mode Bad CSS Customization should've compiled and prefixed",
"CSS Customization production mode Bad CSS Customization should've emitted a source map",
"CSS Customization production mode Basic CSS should compile successfully",
"CSS Customization production mode Basic CSS should've compiled and prefixed",
"CSS Customization production mode Basic CSS should've emitted a source map",
"CSS Customization production mode Correct CSS Customization Array should compile successfully",
"CSS Customization production mode Correct CSS Customization Array should've compiled and prefixed",
"CSS Customization production mode Correct CSS Customization Array should've emitted a source map",
"CSS Customization production mode Correct CSS Customization custom loader should compile successfully",
"CSS Customization production mode Correct CSS Customization custom loader should've applied style"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/css-features/test/browserslist.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Browserslist: New production mode should have compiled successfully",
"Browserslist: New production mode should've emitted a single CSS file",
"Browserslist: Old production mode should have compiled successfully",
"Browserslist: Old production mode should've emitted a single CSS file"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/css-features/test/css-modules.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"CSS Modules: Import Exports production mode should have compiled successfully",
"CSS Modules: Import Exports production mode should've emitted a single CSS file",
"CSS Modules: Import Global CSS production mode should have compiled successfully",
"CSS Modules: Import Global CSS production mode should've emitted a single CSS file",
"CSS Modules: Importing Invalid Global CSS production mode should fail to build",
"Custom Properties: Fail for :root {} in CSS Modules production mode should fail to build",
"Custom Properties: Fail for global element in CSS Modules production mode should fail to build"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/css-features/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Custom Properties: Pass-Through IE11 production mode should have compiled successfully",
"Custom Properties: Pass-Through IE11 production mode should've emitted a single CSS file",
"Custom Properties: Pass-Through Modern production mode should have compiled successfully",
"Custom Properties: Pass-Through Modern production mode should've emitted a single CSS file",
"Inline Comments: Minify production mode should have compiled successfully",
"Inline Comments: Minify production mode should've emitted a single CSS file"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/css-minify/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"css-minify production mode should minify correctly by removing whitespace"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/css-modules/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Can hot reload CSS Module without losing state should update CSS color without remounting <input>",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Has CSS Module in computed styles in Development should have CSS for page"
],
"failed": [],
"pending": [
"3rd Party CSS Module Support production mode should have compiled successfully",
"3rd Party CSS Module Support production mode should've emitted a single CSS file",
"3rd Party CSS Module Support production mode should've injected the CSS on server render",
"Basic CSS Module Support production mode should have compiled successfully",
"Basic CSS Module Support production mode should've emitted a single CSS file",
"Basic CSS Module Support production mode should've injected the CSS on server render",
"CSS Module Composes Usage (Basic) production mode should have compiled successfully",
"CSS Module Composes Usage (Basic) production mode should've emitted a single CSS file",
"CSS Module Composes Usage (External) production mode should have compiled successfully",
"CSS Module Composes Usage (External) production mode should've emitted a single CSS file",
"Catch-all Route CSS Module Usage production mode should apply styles correctly",
"Catch-all Route CSS Module Usage production mode should have compiled successfully",
"Catch-all Route CSS Module Usage production mode should've emitted a single CSS file",
"Dynamic Route CSS Module Usage production mode should apply styles correctly",
"Dynamic Route CSS Module Usage production mode should have compiled successfully",
"Dynamic Route CSS Module Usage production mode should've emitted a single CSS file",
"Has CSS Module in computed styles in Production production mode should have CSS for page",
"Has CSS Module in computed styles in Production production mode should have compiled successfully",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Invalid CSS Module Usage in node_modules production mode should fail to build",
"Invalid Global CSS Module Usage in node_modules production mode should fail to build",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Valid CSS Module Usage from within node_modules production mode should have compiled successfully",
"Valid CSS Module Usage from within node_modules production mode should've emitted a single CSS file",
"Valid CSS Module Usage from within node_modules production mode should've prerendered with relevant data",
"Valid Nested CSS Module Usage from within node_modules production mode should have compiled successfully",
"Valid Nested CSS Module Usage from within node_modules production mode should've emitted a single CSS file",
"Valid Nested CSS Module Usage from within node_modules production mode should've prerendered with relevant data"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/css/test/basic-global-support.test.js": {
"passed": [],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
"pending": [
"Basic Global Support production mode should compile successfully",
"Basic Global Support production mode should've emitted a single CSS file",
"Basic Global Support with special characters in path production mode should compile successfully",
"Basic Global Support with special characters in path production mode should've emitted a single CSS file",
"Basic Global Support with src/ dir production mode should compile successfully",
"Basic Global Support with src/ dir production mode should've emitted a single CSS file",
"CSS URL via `file-loader` and asset prefix (1) production mode should compile successfully",
"CSS URL via `file-loader` and asset prefix (1) production mode should've emitted expected files",
"CSS URL via `file-loader` and asset prefix (2) production mode should compile successfully",
"CSS URL via `file-loader` and asset prefix (2) production mode should've emitted expected files",
"CSS URL via `file-loader` production mode should compile successfully",
"CSS URL via `file-loader` production mode should've emitted expected files",
"Multi Global Support (reversed) production mode should compile successfully",
"Multi Global Support (reversed) production mode should've emitted a single CSS file",
"Multi Global Support production mode should compile successfully",
"Multi Global Support production mode should've emitted a single CSS file",
"Nested @import() Global Support production mode should compile successfully",
"Nested @import() Global Support production mode should've emitted a single CSS file"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/css/test/css-and-styled-jsx.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Ordering with styled-jsx (dev) should have the correct color (css ordering)"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Ordering with styled-jsx (prod) production mode should have compiled successfully",
"Ordering with styled-jsx (prod) production mode should have the correct color (css ordering)"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/css/test/css-compilation.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"CSS Property Ordering production mode should have compiled successfully",
"CSS Property Ordering production mode should have the border width (property ordering)",
"CSS Support production mode CSS Compilation and Prefixing should compile successfully",
"CSS Support production mode CSS Compilation and Prefixing should've compiled and prefixed",
"CSS Support production mode CSS Compilation and Prefixing should've emitted a source map",
"CSS Support production mode Good CSS Import from node_modules should compile successfully",
"CSS Support production mode Good CSS Import from node_modules should've emitted a single CSS file",
"CSS Support production mode Good Nested CSS Import from node_modules should compile successfully",
"CSS Support production mode Good Nested CSS Import from node_modules should've emitted a single CSS file",
"CSS Support production mode Has CSS in computed styles in Production should have CSS for page",
"CSS Support production mode Has CSS in computed styles in Production should have compiled successfully",
"CSS Support production mode Has CSS in computed styles in Production should've preloaded the CSS file and injected it in <head>",
"CSS Support production mode React Lifecyce Order (production) should have compiled successfully",
"CSS Support production mode React Lifecyce Order (production) should have the correct color on mount after navigation"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
"runtimeError": false
},
"test/integration/css/test/css-modules.test.js": {
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"passed": [
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"Basic CSS Modules Ordering Development Mode should have correct color on index page (on hover)",
"Basic CSS Modules Ordering Development Mode should have correct color on index page (on load)",
"Ordering with Global CSS and Modules (dev) should have the correct color (css ordering)",
"Ordering with Global CSS and Modules (dev) should have the correct color (css ordering) during hot reloads",
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"Ordering with Global CSS and Modules (dev) should not execute scripts in any order"
],
"failed": [
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Basic CSS Modules Ordering Development Mode should have correct color on index page (on nav)",
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"CSS Modules Composes Ordering Development Mode should have correct color on index page (on hover)",
"CSS Modules Composes Ordering Development Mode should have correct color on index page (on load)"
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"Basic CSS Modules Ordering production mode should have correct color on index page (on hover)",
"Basic CSS Modules Ordering production mode should have correct color on index page (on load)",
"Basic CSS Modules Ordering production mode should have correct color on index page (on nav)",
"CSS Modules Composes Ordering production mode should have correct CSS injection order",
"CSS Modules Composes Ordering production mode should have correct color on index page (on hover)",
"CSS Modules Composes Ordering production mode should have correct color on index page (on load)",
"CSS Modules Composes Ordering production mode should have correct color on index page (on nav from index)",
"CSS Modules Composes Ordering production mode should have correct color on index page (on nav from other)",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"CSS Modules Composes Ordering production mode should not change color on hover",
"Data URLs production mode should compile successfully",
"Data URLs production mode should have emitted expected files",
"Ordering with Global CSS and Modules (prod) production mode should have compiled successfully",
"Ordering with Global CSS and Modules (prod) production mode should have the correct color (css ordering)",
"should handle unresolved files gracefully production mode should build correctly",
"should handle unresolved files gracefully production mode should have correct file references in CSS output"
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"flakey": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"CSS Modules Composes Ordering Development Mode should have correct color on index page (on nav from index)",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"CSS Modules Composes Ordering Development Mode should have correct color on index page (on nav from other)"
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/css/test/css-rendering.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"failed": [],
"pending": [
"CSS Support CSS Cleanup on Render Failure production mode not have intermediary page styles on error rendering",
"CSS Support CSS page transition inject <style> with nonce so it works with CSP header production mode should have correct CSS injection order",
"CSS Support CSS page transition inject <style> with nonce so it works with CSP header production mode should have correct color on index page (on hover)",
"CSS Support CSS page transition inject <style> with nonce so it works with CSP header production mode should have correct color on index page (on load)",
"CSS Support CSS page transition inject <style> with nonce so it works with CSP header production mode should have correct color on index page (on nav from index)",
"CSS Support CSS page transition inject <style> with nonce so it works with CSP header production mode should have correct color on index page (on nav from other)",
"CSS Support CSS page transition inject <style> with nonce so it works with CSP header production mode should not change color on hover",
"CSS Support Page hydrates with CSS and not waiting on dependencies production mode should hydrate black without dependencies manifest",
"CSS Support Page hydrates with CSS and not waiting on dependencies production mode should hydrate red without dependencies manifest",
"CSS Support Page hydrates with CSS and not waiting on dependencies production mode should route from black to red without dependencies",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"CSS Support Page reload on CSS missing production mode should fall back to server-side transition on missing CSS",
"CSS Support production mode CSS Import from node_modules should fail the build"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/css/test/dev-css-handling.test.js": {
"passed": [
"Body is not hidden when broken in Development should have body visible",
"Body is not hidden when unused in Development should have body visible",
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"Can hot reload CSS without losing state should update CSS color without remounting <input>",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Has CSS in computed styles in Development should have CSS for page",
"React Lifecyce Order (dev) should have the correct color on mount after navigation"
],
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/css/test/valid-invalid-css.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Invalid CSS in _document production mode should fail to build",
"Invalid Global CSS production mode should fail to build",
"Invalid Global CSS with Custom App production mode should fail to build",
"Valid Global CSS from npm production mode should compile successfully",
"Valid Global CSS from npm production mode should've emitted a single CSS file",
"Valid and Invalid Global CSS with Custom App production mode should fail to build"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/custom-error-page-exception/test/index.test.js": {
"passed": [],
"failed": [],
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Custom error page exception production mode should handle errors from _error render"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/custom-error/test/index.test.js": {
feat(turbopack): port bloom filter to nexturbo (#55678) Closes WEB-1096
2023-09-28 03:00:49 +02:00
"passed": [],
"failed": [],
"pending": [],
"flakey": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Custom _error dev mode 1 should not warn with /_error and /404 when rendering error first",
"Custom _error dev mode 2 should not warn with /_error and /404",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Custom _error dev mode 2 should warn on custom /_error without custom /404",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Custom _error production mode renders custom _error successfully",
"Custom _error production mode should not contain /_error in build output"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/custom-page-extension/test/index.test.js": {
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Custom page extension dev mode should work dynamic page",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Custom page extension dev mode should work with normal page"
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Custom page extension production mode should work dynamic page",
"Custom page extension production mode should work with normal page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/custom-routes-catchall/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Custom routes dev mode should rewrite and render page correctly",
"Custom routes dev mode should rewrite to /_next/static correctly",
"Custom routes dev mode should rewrite to public file correctly",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Custom routes dev mode should rewrite to public/static correctly"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Custom routes production mode should rewrite and render page correctly",
"Custom routes production mode should rewrite to /_next/static correctly",
"Custom routes production mode should rewrite to public file correctly",
"Custom routes production mode should rewrite to public/static correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/custom-routes-i18n-index-redirect/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Custom routes i18n with index redirect dev mode should respond to default locale redirects correctly for index redirect"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"Custom routes i18n with index redirect production mode should respond to default locale redirects correctly for index redirect"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/custom-routes-i18n/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Custom routes i18n dev mode should navigate on the client with rewrites correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Custom routes i18n dev mode should respond to default locale redirects correctly",
"Custom routes i18n dev mode should rewrite correctly",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Custom routes i18n dev mode should rewrite index routes correctly"
],
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"Custom routes i18n production mode should navigate on the client with rewrites correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Custom routes i18n production mode should respond to default locale redirects correctly",
"Custom routes i18n production mode should rewrite correctly",
"Custom routes i18n production mode should rewrite index routes correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
"runtimeError": false
},
"test/integration/custom-routes/test/index.test.js": {
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"passed": [
"Custom routes dev mode should add refresh header for 308 redirect",
"Custom routes dev mode should allow params in query for redirect",
"Custom routes dev mode should allow params in query for rewrite",
"Custom routes dev mode should allow redirecting to external resource",
"Custom routes dev mode should apply headers for exact match",
"Custom routes dev mode should apply headers for multi match",
"Custom routes dev mode should apply params for header key/values",
"Custom routes dev mode should apply params header key/values with URL",
"Custom routes dev mode should apply params header key/values with URL that has port",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Custom routes dev mode should continue in beforeFiles rewrites",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Custom routes dev mode should double redirect successfully",
"Custom routes dev mode should handle api rewrite with param successfully",
"Custom routes dev mode should handle api rewrite with un-named param successfully",
"Custom routes dev mode should handle basic api rewrite successfully",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Custom routes dev mode should handle beforeFiles rewrite to dynamic route correctly",
"Custom routes dev mode should handle beforeFiles rewrite to partly dynamic route correctly",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Custom routes dev mode should handle chained redirects successfully",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Custom routes dev mode should handle chained rewrites successfully",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Custom routes dev mode should handle encoded value in the pathname correctly",
"Custom routes dev mode should handle has query encoding correctly",
"Custom routes dev mode should handle named regex parameters with multi-match successfully",
"Custom routes dev mode should handle one-to-one rewrite successfully",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Custom routes dev mode should handle param like headers properly",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Custom routes dev mode should handle query for rewrite correctly",
"Custom routes dev mode should handle unnamed parameters with multi-match successfully",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Custom routes dev mode should have correct encoding for params with catchall rewrite",
"Custom routes dev mode should have correct header for catchall rewrite",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Custom routes dev mode should have correct params for catchall rewrite",
"Custom routes dev mode should have correct query for catchall rewrite",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Custom routes dev mode should have correctly encoded params in query for redirect",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Custom routes dev mode should have correctly encoded query in location and refresh headers",
"Custom routes dev mode should honor caseSensitiveRoutes config for /HELLO-world",
"Custom routes dev mode should honor caseSensitiveRoutes config for /add-HEADER",
"Custom routes dev mode should honor caseSensitiveRoutes config for /docs/GITHUB",
"Custom routes dev mode should honor caseSensitiveRoutes config for /to-ANOTHER",
"Custom routes dev mode should match /_next file after rewrite",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Custom routes dev mode should match a page after a rewrite",
"Custom routes dev mode should match dynamic route after rewrite",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Custom routes dev mode should match has cookie for header correctly",
"Custom routes dev mode should match has cookie redirect correctly",
"Custom routes dev mode should match has cookie rewrite correctly",
"Custom routes dev mode should match has header for header correctly",
"Custom routes dev mode should match has header redirect correctly",
"Custom routes dev mode should match has header rewrite correctly",
"Custom routes dev mode should match has host for header correctly",
"Custom routes dev mode should match has host redirect and insert in destination correctly",
"Custom routes dev mode should match has host redirect correctly",
"Custom routes dev mode should match has host rewrite correctly",
"Custom routes dev mode should match has query for header correctly",
"Custom routes dev mode should match has query redirect correctly",
"Custom routes dev mode should match has query redirect with duplicate query key",
"Custom routes dev mode should match has query rewrite correctly",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Custom routes dev mode should match has rewrite correctly before files",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Custom routes dev mode should match missing cookie headers correctly",
"Custom routes dev mode should match missing cookie redirect correctly",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Custom routes dev mode should match missing cookie rewrite correctly",
"Custom routes dev mode should match missing header headers correctly",
"Custom routes dev mode should match missing header redirect correctly",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Custom routes dev mode should match missing header rewrite correctly",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Custom routes dev mode should match missing query headers correctly",
"Custom routes dev mode should match missing query redirect correctly",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Custom routes dev mode should match missing query rewrite correctly",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Custom routes dev mode should match public file after rewrite",
"Custom routes dev mode should not allow rewrite to override page file",
"Custom routes dev mode should not append params when one is used in destination path",
"Custom routes dev mode should not hang when proxy rewrite fails",
"Custom routes dev mode should not match dynamic route immediately after applying header",
"Custom routes dev mode should not match redirect for /_next",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Custom routes dev mode should not pass non captured has value for rewrite correctly",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Custom routes dev mode should not rewrite for _next/data route when a match is found",
"Custom routes dev mode should overwrite param values correctly",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Custom routes dev mode should parse params correctly for rewrite to auto-export dynamic page",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Custom routes dev mode should pass captured has value for rewrite correctly",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Custom routes dev mode should pass has segment for rewrite correctly",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Custom routes dev mode should provide params correctly for rewrite to auto-export non-dynamic page",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Custom routes dev mode should redirect successfully with catchall",
"Custom routes dev mode should redirect successfully with permanent: false",
"Custom routes dev mode should redirect successfully with provided statusCode",
"Custom routes dev mode should redirect with URL in query correctly",
"Custom routes dev mode should redirect with URL in query correctly non-encoded",
"Custom routes dev mode should redirect with hash successfully",
"Custom routes dev mode should redirect with params successfully",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Custom routes dev mode should resolveHref correctly navigating through history",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Custom routes dev mode should rewrite with params successfully",
"Custom routes dev mode should server static files through a rewrite",
"Custom routes dev mode should successfully rewrite a WebSocket request",
"Custom routes dev mode should successfully rewrite a WebSocket request to a page",
"Custom routes dev mode should support URL for header key/values",
"Custom routes dev mode should support long URLs for rewrites",
"Custom routes dev mode should support named like unnamed parameters correctly",
"Custom routes dev mode should support named pattern for header key/values",
"Custom routes dev mode should support proxying to external resource",
"Custom routes dev mode should support unnamed parameters correctly",
"Custom routes dev mode should work successfully on the client",
"Custom routes dev mode should work with rewrite when manually specifying href/as",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Custom routes dev mode should work with rewrite when only specifying href",
"Custom routes dev mode should work with rewrite when only specifying href and ends in dynamic route",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Custom routes dev mode show allow redirect to override the page",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Custom routes no-op rewrite should not error for no-op rewrite and auto export dynamic route",
"Custom routes should load custom routes when only one type is used dev mode should work with just headers",
"Custom routes should load custom routes when only one type is used dev mode should work with just redirects",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Custom routes should load custom routes when only one type is used dev mode should work with just rewrites"
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"failed": [
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Custom routes dev mode should handle external beforeFiles rewrite correctly"
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
],
"pending": [
"Custom routes production mode should add refresh header for 308 redirect",
"Custom routes production mode should allow params in query for redirect",
"Custom routes production mode should allow params in query for rewrite",
"Custom routes production mode should allow redirecting to external resource",
"Custom routes production mode should apply headers for exact match",
"Custom routes production mode should apply headers for multi match",
"Custom routes production mode should apply params for header key/values",
"Custom routes production mode should apply params header key/values with URL",
"Custom routes production mode should apply params header key/values with URL that has port",
"Custom routes production mode should continue in beforeFiles rewrites",
"Custom routes production mode should double redirect successfully",
"Custom routes production mode should handle api rewrite with param successfully",
"Custom routes production mode should handle api rewrite with un-named param successfully",
"Custom routes production mode should handle basic api rewrite successfully",
"Custom routes production mode should handle beforeFiles rewrite to dynamic route correctly",
"Custom routes production mode should handle beforeFiles rewrite to partly dynamic route correctly",
"Custom routes production mode should handle chained redirects successfully",
"Custom routes production mode should handle chained rewrites successfully",
"Custom routes production mode should handle encoded value in the pathname correctly",
"Custom routes production mode should handle external beforeFiles rewrite correctly",
"Custom routes production mode should handle has query encoding correctly",
"Custom routes production mode should handle named regex parameters with multi-match successfully",
"Custom routes production mode should handle one-to-one rewrite successfully",
"Custom routes production mode should handle param like headers properly",
"Custom routes production mode should handle query for rewrite correctly",
"Custom routes production mode should handle unnamed parameters with multi-match successfully",
"Custom routes production mode should have correct encoding for params with catchall rewrite",
"Custom routes production mode should have correct header for catchall rewrite",
"Custom routes production mode should have correct params for catchall rewrite",
"Custom routes production mode should have correct query for catchall rewrite",
"Custom routes production mode should have correctly encoded params in query for redirect",
"Custom routes production mode should have correctly encoded query in location and refresh headers",
"Custom routes production mode should have redirects/rewrites in build output with debug flag",
"Custom routes production mode should honor caseSensitiveRoutes config for /HELLO-world",
"Custom routes production mode should honor caseSensitiveRoutes config for /add-HEADER",
"Custom routes production mode should honor caseSensitiveRoutes config for /docs/GITHUB",
"Custom routes production mode should honor caseSensitiveRoutes config for /to-ANOTHER",
"Custom routes production mode should match /_next file after rewrite",
"Custom routes production mode should match a page after a rewrite",
"Custom routes production mode should match dynamic route after rewrite",
"Custom routes production mode should match has cookie for header correctly",
"Custom routes production mode should match has cookie redirect correctly",
"Custom routes production mode should match has cookie rewrite correctly",
"Custom routes production mode should match has header for header correctly",
"Custom routes production mode should match has header redirect correctly",
"Custom routes production mode should match has header rewrite correctly",
"Custom routes production mode should match has host for header correctly",
"Custom routes production mode should match has host redirect and insert in destination correctly",
"Custom routes production mode should match has host redirect correctly",
"Custom routes production mode should match has host rewrite correctly",
"Custom routes production mode should match has query for header correctly",
"Custom routes production mode should match has query redirect correctly",
"Custom routes production mode should match has query redirect with duplicate query key",
"Custom routes production mode should match has query rewrite correctly",
"Custom routes production mode should match has rewrite correctly before files",
"Custom routes production mode should match missing cookie headers correctly",
"Custom routes production mode should match missing cookie redirect correctly",
"Custom routes production mode should match missing cookie rewrite correctly",
"Custom routes production mode should match missing header headers correctly",
"Custom routes production mode should match missing header redirect correctly",
"Custom routes production mode should match missing header rewrite correctly",
"Custom routes production mode should match missing query headers correctly",
"Custom routes production mode should match missing query redirect correctly",
"Custom routes production mode should match missing query rewrite correctly",
"Custom routes production mode should match public file after rewrite",
"Custom routes production mode should not allow rewrite to override page file",
"Custom routes production mode should not append params when one is used in destination path",
"Custom routes production mode should not hang when proxy rewrite fails",
"Custom routes production mode should not match dynamic route immediately after applying header",
"Custom routes production mode should not match redirect for /_next",
"Custom routes production mode should not pass non captured has value for rewrite correctly",
"Custom routes production mode should not rewrite for _next/data route when a match is found",
"Custom routes production mode should not show warning for custom routes when not next export",
"Custom routes production mode should output routes-manifest successfully",
"Custom routes production mode should overwrite param values correctly",
"Custom routes production mode should parse params correctly for rewrite to auto-export dynamic page",
"Custom routes production mode should pass captured has value for rewrite correctly",
"Custom routes production mode should pass has segment for rewrite correctly",
"Custom routes production mode should provide params correctly for rewrite to auto-export non-dynamic page",
"Custom routes production mode should redirect successfully with catchall",
"Custom routes production mode should redirect successfully with permanent: false",
"Custom routes production mode should redirect successfully with provided statusCode",
"Custom routes production mode should redirect with URL in query correctly",
"Custom routes production mode should redirect with URL in query correctly non-encoded",
"Custom routes production mode should redirect with hash successfully",
"Custom routes production mode should redirect with params successfully",
"Custom routes production mode should resolveHref correctly navigating through history",
"Custom routes production mode should rewrite with params successfully",
"Custom routes production mode should server static files through a rewrite",
"Custom routes production mode should successfully rewrite a WebSocket request",
"Custom routes production mode should successfully rewrite a WebSocket request to a page",
"Custom routes production mode should support URL for header key/values",
"Custom routes production mode should support long URLs for rewrites",
"Custom routes production mode should support named like unnamed parameters correctly",
"Custom routes production mode should support named pattern for header key/values",
"Custom routes production mode should support proxying to external resource",
"Custom routes production mode should support unnamed parameters correctly",
"Custom routes production mode should work successfully on the client",
"Custom routes production mode should work with rewrite when manually specifying href/as",
"Custom routes production mode should work with rewrite when only specifying href",
"Custom routes production mode should work with rewrite when only specifying href and ends in dynamic route",
"Custom routes production mode show allow redirect to override the page",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Custom routes should load custom routes when only one type is used production mode should work with just headers",
"Custom routes should load custom routes when only one type is used production mode should work with just redirects",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"Custom routes should load custom routes when only one type is used production mode should work with just rewrites",
"export production mode should not show warning for custom routes when not next export"
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/custom-server-types/test/index.test.js": {
"passed": ["Custom Server TypeScript should build server.ts correctly"],
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/custom-server/test/index.test.js": {
"passed": [],
"failed": [],
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Custom Server using HTTP Error when rendering without starting slash production mode should warn in production mode",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Custom Server using HTTP Error when rendering without starting slash should warn in dev mode",
"Custom Server using HTTP HMR with custom server Should support HMR when rendering with /index pathname",
"Custom Server using HTTP compression handling should handle compression for route /",
"Custom Server using HTTP compression handling should handle compression for route /no-query",
"Custom Server using HTTP unhandled rejection stderr should include error message and stack trace",
"Custom Server using HTTP with a custom fetch polyfill should serve internal file from render",
"Custom Server using HTTP with dynamic assetPrefix should contain customServer in NEXT_DATA",
"Custom Server using HTTP with dynamic assetPrefix should handle custom urls with requests handler",
"Custom Server using HTTP with dynamic assetPrefix should handle null assetPrefix accordingly",
"Custom Server using HTTP with dynamic assetPrefix should handle render with undefined query",
"Custom Server using HTTP with dynamic assetPrefix should render nested index",
"Custom Server using HTTP with dynamic assetPrefix should serve internal file from render",
"Custom Server using HTTP with dynamic assetPrefix should set the assetPrefix dynamically",
"Custom Server using HTTP with dynamic assetPrefix should set the assetPrefix to a given request",
"Custom Server using HTTP with generateEtags disabled response does not include etag header",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Custom Server using HTTP with generateEtags enabled production mode response includes etag header",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Custom Server using HTTP with middleware $title should read the expected url protocol in middleware",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Custom Server using HTTPS Error when rendering without starting slash production mode should warn in production mode",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Custom Server using HTTPS Error when rendering without starting slash should warn in dev mode",
"Custom Server using HTTPS compression handling should handle compression for route /",
"Custom Server using HTTPS compression handling should handle compression for route /no-query",
"Custom Server using HTTPS unhandled rejection stderr should include error message and stack trace",
"Custom Server using HTTPS with a custom fetch polyfill should serve internal file from render",
"Custom Server using HTTPS with dynamic assetPrefix should contain customServer in NEXT_DATA",
"Custom Server using HTTPS with dynamic assetPrefix should handle custom urls with requests handler",
"Custom Server using HTTPS with dynamic assetPrefix should handle null assetPrefix accordingly",
"Custom Server using HTTPS with dynamic assetPrefix should handle render with undefined query",
"Custom Server using HTTPS with dynamic assetPrefix should render nested index",
"Custom Server using HTTPS with dynamic assetPrefix should serve internal file from render",
"Custom Server using HTTPS with dynamic assetPrefix should set the assetPrefix dynamically",
"Custom Server using HTTPS with dynamic assetPrefix should set the assetPrefix to a given request",
"Custom Server using HTTPS with generateEtags disabled response does not include etag header",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Custom Server using HTTPS with generateEtags enabled production mode response includes etag header",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Custom Server using HTTPS with middleware $title should read the expected url protocol in middleware"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/data-fetching-errors/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"GS(S)P Page Errors dev mode should show error for getServerSideProps as component member",
"GS(S)P Page Errors dev mode should show error for getStaticPaths as component member",
"GS(S)P Page Errors dev mode should show error for getStaticProps as component member",
"GS(S)P Page Errors dev mode should show error for undefined getServerSideProps",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"GS(S)P Page Errors dev mode should show error for undefined getStaticProps"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"GS(S)P Page Errors production mode Error stack printed to stderr",
"GS(S)P Page Errors production mode should show error for getServerSideProps as component member",
"GS(S)P Page Errors production mode should show error for getStaticPaths as component member",
"GS(S)P Page Errors production mode should show error for getStaticProps as component member",
"GS(S)P Page Errors production mode should show error for undefined getStaticProps"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/dedupes-scripts/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"De-dedupes scripts in _document production mode Does not have duplicate script references"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/development-hmr-refresh/test/index.test.js": {
"passed": ["page should not reload when the file is not changed"],
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/development-runtime-config/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"should work with runtime-config in next.config.js empty runtime-config",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"should work with runtime-config in next.config.js with runtime-config"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/disable-js/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"disabled runtime JS dev mode should have a script for each preload link",
"disabled runtime JS dev mode should not have __NEXT_DATA__ script",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"disabled runtime JS dev mode should render the page"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"disabled runtime JS production mode should not have __NEXT_DATA__ script",
"disabled runtime JS production mode should not have preload links",
"disabled runtime JS production mode should not have scripts",
"disabled runtime JS production mode should render the page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/dist-dir/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"distDir dev mode should build the app within the given `dist` directory",
"distDir dev mode should not build the app within the default `.next` directory",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"distDir dev mode should render the page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"distDir With basic usage production mode should build the app within the given `dist` directory",
"distDir With basic usage production mode should not build the app within the default `.next` directory",
"distDir With basic usage production mode should render the page",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"distDir production mode should handle undefined distDir",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"distDir production mode should throw error with invalid distDir"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/document-file-dependencies/test/index.test.js": {
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"passed": [],
"failed": [],
"pending": [
"File Dependencies production mode should apply styles defined in global and module css files in 404 page",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"File Dependencies production mode should apply styles defined in global and module css files in a standard page.",
"File Dependencies production mode should apply styles defined in global and module css files in error page"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/document-head-warnings/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Custom Document Head Warnings development mode warns when using a <title> in document/head",
"Custom Document Head Warnings development mode warns when using a crossOrigin attribute on document/head",
"Custom Document Head Warnings development mode warns when using viewport meta tags in document/head"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/draft-mode/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Test Draft Mode Development Mode should disable draft mode",
"Test Draft Mode Development Mode should enable draft mode",
"Test Draft Mode Development Mode should fetch draft data on CST",
"Test Draft Mode Development Mode should fetch draft data on SSR",
"Test Draft Mode Development Mode should return cookies to be expired after dev server reboot",
"Test Draft Mode Development Mode should start development application",
"Test Draft Mode Development Mode should start the client-side browser"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
"pending": [
"Test Draft Mode production mode should compile successfully",
"Test Draft Mode production mode should enable draft mode",
"Test Draft Mode production mode should not return fallback page on draft request",
"Test Draft Mode production mode should pass draft mode to API routes",
"Test Draft Mode production mode should pass undefined to API routes when not in draft mode",
"Test Draft Mode production mode should return cookies to be expired on disable request",
"Test Draft Mode production mode should return correct caching headers for draft mode request",
"Test Draft Mode production mode should return dynamic response when draft mode enabled",
"Test Draft Mode production mode should return prerendered page on first request",
"Test Draft Mode production mode should return prerendered page on second request",
"Test Draft Mode production mode should start production application"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/dynamic-optional-routing-root-fallback/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic Optional Routing Root Fallback dev mode should render optional catch-all top-level route with no segments",
"Dynamic Optional Routing Root Fallback dev mode should render optional catch-all top-level route with one segment",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Dynamic Optional Routing Root Fallback dev mode should render optional catch-all top-level route with two segments"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic Optional Routing Root Fallback production mode should render optional catch-all top-level route with no segments",
"Dynamic Optional Routing Root Fallback production mode should render optional catch-all top-level route with one segment",
"Dynamic Optional Routing Root Fallback production mode should render optional catch-all top-level route with two segments"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/dynamic-optional-routing-root-static-paths/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic Optional Routing dev mode should render optional catch-all top-level route with no segments",
"Dynamic Optional Routing dev mode should render optional catch-all top-level route with one segment",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Dynamic Optional Routing dev mode should render optional catch-all top-level route with two segments"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic Optional Routing production mode should render optional catch-all top-level route with no segments",
"Dynamic Optional Routing production mode should render optional catch-all top-level route with one segment",
"Dynamic Optional Routing production mode should render optional catch-all top-level route with two segments"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/dynamic-optional-routing/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic Optional Routing dev mode should fail to build when mixed with regular catch-all",
"Dynamic Optional Routing dev mode should fail to build when optional but no catch-all",
"Dynamic Optional Routing dev mode should fail to build when optional route has index.js at root",
"Dynamic Optional Routing dev mode should fail to build when optional route has same page at root",
"Dynamic Optional Routing dev mode should fall back to top-level catch-all",
"Dynamic Optional Routing dev mode should fallback correctly when fallback enabled",
"Dynamic Optional Routing dev mode should handle getStaticPaths 1 segment",
"Dynamic Optional Routing dev mode should handle getStaticPaths 1 segment and trailing slash",
"Dynamic Optional Routing dev mode should handle getStaticPaths 2 segments",
"Dynamic Optional Routing dev mode should handle getStaticPaths 2 segments and trailing slash",
"Dynamic Optional Routing dev mode should handle getStaticPaths no segments",
"Dynamic Optional Routing dev mode should handle getStaticPaths no segments and trailing slash",
"Dynamic Optional Routing dev mode should handle getStaticPaths with fallback 2 segments",
"Dynamic Optional Routing dev mode should handle getStaticPaths with fallback no segments",
"Dynamic Optional Routing dev mode should match catch-all api route with multiple segments",
"Dynamic Optional Routing dev mode should match catch-all api route with no segments",
"Dynamic Optional Routing dev mode should match catch-all api route with no segments and leading slash",
"Dynamic Optional Routing dev mode should match catch-all api route with single segment",
"Dynamic Optional Routing dev mode should match root path on false param",
"Dynamic Optional Routing dev mode should match root path on null param",
"Dynamic Optional Routing dev mode should match root path on undefined param",
"Dynamic Optional Routing dev mode should render catch-all nested route with multiple segments",
"Dynamic Optional Routing dev mode should render catch-all nested route with no segments",
"Dynamic Optional Routing dev mode should render catch-all nested route with no segments and leading slash",
"Dynamic Optional Routing dev mode should render catch-all nested route with single segment",
"Dynamic Optional Routing dev mode should render catch-all top-level route with multiple segments",
"Dynamic Optional Routing dev mode should render catch-all top-level route with no segments",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Dynamic Optional Routing dev mode should render catch-all top-level route with single segment"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic Optional Routing production mode should fail to build when mixed with regular catch-all",
"Dynamic Optional Routing production mode should fail to build when optional but no catch-all",
"Dynamic Optional Routing production mode should fail to build when optional route has index.js at root",
"Dynamic Optional Routing production mode should fail to build when optional route has same page at root",
"Dynamic Optional Routing production mode should fail to build when param is not explicitly defined",
"Dynamic Optional Routing production mode should fall back to top-level catch-all",
"Dynamic Optional Routing production mode should fallback correctly when fallback enabled",
"Dynamic Optional Routing production mode should handle getStaticPaths 1 segment",
"Dynamic Optional Routing production mode should handle getStaticPaths 1 segment and trailing slash",
"Dynamic Optional Routing production mode should handle getStaticPaths 2 segments",
"Dynamic Optional Routing production mode should handle getStaticPaths 2 segments and trailing slash",
"Dynamic Optional Routing production mode should handle getStaticPaths no segments",
"Dynamic Optional Routing production mode should handle getStaticPaths no segments and trailing slash",
"Dynamic Optional Routing production mode should handle getStaticPaths with fallback 2 segments",
"Dynamic Optional Routing production mode should handle getStaticPaths with fallback no segments",
"Dynamic Optional Routing production mode should match catch-all api route with multiple segments",
"Dynamic Optional Routing production mode should match catch-all api route with no segments",
"Dynamic Optional Routing production mode should match catch-all api route with no segments and leading slash",
"Dynamic Optional Routing production mode should match catch-all api route with single segment",
"Dynamic Optional Routing production mode should match root path on false param",
"Dynamic Optional Routing production mode should match root path on null param",
"Dynamic Optional Routing production mode should match root path on undefined param",
"Dynamic Optional Routing production mode should render catch-all nested route with multiple segments",
"Dynamic Optional Routing production mode should render catch-all nested route with no segments",
"Dynamic Optional Routing production mode should render catch-all nested route with no segments and leading slash",
"Dynamic Optional Routing production mode should render catch-all nested route with single segment",
"Dynamic Optional Routing production mode should render catch-all top-level route with multiple segments",
"Dynamic Optional Routing production mode should render catch-all top-level route with no segments",
"Dynamic Optional Routing production mode should render catch-all top-level route with single segment"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/dynamic-require/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic require should not throw error when dynamic require is used"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/dynamic-route-rename/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic route rename casing should not throw error when changing casing of dynamic route file"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/dynamic-routing/test/index.test.js": {
"passed": [
"Dynamic Routing dev mode [catch all] should not decode slashes (end)",
"Dynamic Routing dev mode [catch all] should not decode slashes (middle)",
"Dynamic Routing dev mode [catch all] should not decode slashes (start)",
"Dynamic Routing dev mode [catch all] should not match root on SSR",
"Dynamic Routing dev mode [catch all] should pass param in getInitialProps during SSR",
"Dynamic Routing dev mode [catch all] should pass params in getInitialProps during SSR",
"Dynamic Routing dev mode [catch all] should strip trailing slash",
"Dynamic Routing dev mode [catch-all] should pass params in getInitialProps during client navigation (encoded)",
"Dynamic Routing dev mode [catch-all] should pass params in getInitialProps during client navigation (multi)",
"Dynamic Routing dev mode [catch-all] should pass params in getInitialProps during client navigation (single)",
"Dynamic Routing dev mode [catch-all] shouldn't fail on colon followed by double digits in the path",
"Dynamic Routing dev mode [nested ssg: catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing dev mode [nested ssg: catch all] should pass params in getStaticProps during SSR",
"Dynamic Routing dev mode [nested ssg: catch-all] should pass params in getStaticProps during client navigation (multi)",
"Dynamic Routing dev mode [nested ssg: catch-all] should pass params in getStaticProps during client navigation (single)",
"Dynamic Routing dev mode [predefined ssg: catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing dev mode [predefined ssg: catch all] should pass params in getStaticProps during SSR",
"Dynamic Routing dev mode [predefined ssg: prerendered catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing dev mode [predefined ssg: prerendered catch all] should pass params in getStaticProps during SSR",
"Dynamic Routing dev mode [ssg: catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing dev mode [ssg: catch all] should pass params in getStaticProps during SSR",
"Dynamic Routing dev mode [ssg: catch-all] should pass params in getStaticProps during client navigation (multi interpolated)",
"Dynamic Routing dev mode [ssg: catch-all] should pass params in getStaticProps during client navigation (multi)",
"Dynamic Routing dev mode [ssg: catch-all] should pass params in getStaticProps during client navigation (multi) no as",
"Dynamic Routing dev mode [ssg: catch-all] should pass params in getStaticProps during client navigation (single interpolated)",
"Dynamic Routing dev mode [ssg: catch-all] should pass params in getStaticProps during client navigation (single)",
"Dynamic Routing dev mode should allow calling Router.push on mount successfully",
"Dynamic Routing dev mode should handle only hash on dynamic route",
"Dynamic Routing dev mode should handle only query on dynamic route",
"Dynamic Routing dev mode should navigate optional dynamic page",
"Dynamic Routing dev mode should navigate optional dynamic page with value",
"Dynamic Routing dev mode should navigate to a dynamic page successfully",
"Dynamic Routing dev mode should navigate to a dynamic page successfully interpolated",
"Dynamic Routing dev mode should navigate to a dynamic page successfully interpolated with additional query values",
"Dynamic Routing dev mode should navigate to a dynamic page successfully no as",
"Dynamic Routing dev mode should navigate to a dynamic page with href with differing query and as correctly",
"Dynamic Routing dev mode should navigate to a nested dynamic page successfully",
"Dynamic Routing dev mode should navigate to a nested dynamic page successfully interpolated",
"Dynamic Routing dev mode should navigate to a nested dynamic page successfully no as",
"Dynamic Routing dev mode should navigate with hash to dynamic route with link",
"Dynamic Routing dev mode should navigate with hash to dynamic route with router",
"Dynamic Routing dev mode should not error when requesting dynamic page with /api",
"Dynamic Routing dev mode should not have any console warnings on initial load",
"Dynamic Routing dev mode should not have any console warnings when navigating to dynamic route",
"Dynamic Routing dev mode should not have any query values when not defined",
"Dynamic Routing dev mode should not have placeholder query values for SSS",
"Dynamic Routing dev mode should not preload buildManifest for non-auto export dynamic pages",
"Dynamic Routing dev mode should pass params in getInitialProps during SSR",
"Dynamic Routing dev mode should pass params in getInitialProps during client navigation",
"Dynamic Routing dev mode should prioritize a non-dynamic page",
"Dynamic Routing dev mode should prioritize public files over dynamic route",
"Dynamic Routing dev mode should render another normal route",
"Dynamic Routing dev mode should render dynamic page",
"Dynamic Routing dev mode should render dynamic route with query",
"Dynamic Routing dev mode should render nested dynamic page",
"Dynamic Routing dev mode should render nested optional dynamic page",
"Dynamic Routing dev mode should render normal route",
"Dynamic Routing dev mode should render optional dynamic page",
"Dynamic Routing dev mode should respond with bad request with invalid encoding",
"Dynamic Routing dev mode should scroll to a hash on client-side navigation",
"Dynamic Routing dev mode should scroll to a hash on mount",
"Dynamic Routing dev mode should serve file from public folder encoded",
"Dynamic Routing dev mode should serve file from static folder encoded",
"Dynamic Routing dev mode should serve file with %20 from public folder",
"Dynamic Routing dev mode should serve file with %20 from static folder",
"Dynamic Routing dev mode should serve file with plus from public folder",
"Dynamic Routing dev mode should serve file with plus from static folder",
"Dynamic Routing dev mode should serve file with space from public folder",
"Dynamic Routing dev mode should serve file with space from static folder",
"Dynamic Routing dev mode should show error when interpolating fails for href",
"Dynamic Routing dev mode should support long URLs for dynamic routes",
"Dynamic Routing dev mode should update dynamic values on mount",
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"Dynamic Routing dev mode should update with a hash in the URL"
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
],
"failed": [
"Dynamic Routing dev mode should resolve dynamic route href for page added later"
],
"pending": [
"Dynamic Routing dev mode should not have error after pinging WebSocket",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic Routing production mode [catch all] should not decode slashes (end)",
"Dynamic Routing production mode [catch all] should not decode slashes (middle)",
"Dynamic Routing production mode [catch all] should not decode slashes (start)",
"Dynamic Routing production mode [catch all] should not match root on SSR",
"Dynamic Routing production mode [catch all] should pass param in getInitialProps during SSR",
"Dynamic Routing production mode [catch all] should pass params in getInitialProps during SSR",
"Dynamic Routing production mode [catch all] should strip trailing slash",
"Dynamic Routing production mode [catch-all] should pass params in getInitialProps during client navigation (encoded)",
"Dynamic Routing production mode [catch-all] should pass params in getInitialProps during client navigation (multi)",
"Dynamic Routing production mode [catch-all] should pass params in getInitialProps during client navigation (single)",
"Dynamic Routing production mode [catch-all] shouldn't fail on colon followed by double digits in the path",
"Dynamic Routing production mode [nested ssg: catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing production mode [nested ssg: catch all] should pass params in getStaticProps during SSR",
"Dynamic Routing production mode [nested ssg: catch-all] should pass params in getStaticProps during client navigation (multi)",
"Dynamic Routing production mode [nested ssg: catch-all] should pass params in getStaticProps during client navigation (single)",
"Dynamic Routing production mode [predefined ssg: catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing production mode [predefined ssg: catch all] should pass params in getStaticProps during SSR",
"Dynamic Routing production mode [predefined ssg: prerendered catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing production mode [predefined ssg: prerendered catch all] should pass params in getStaticProps during SSR",
"Dynamic Routing production mode [ssg: catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing production mode [ssg: catch all] should pass params in getStaticProps during SSR",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Dynamic Routing production mode [ssg: catch-all] should pass params in getStaticProps during client navigation (multi interpolated)",
"Dynamic Routing production mode [ssg: catch-all] should pass params in getStaticProps during client navigation (multi)",
"Dynamic Routing production mode [ssg: catch-all] should pass params in getStaticProps during client navigation (multi) no as",
"Dynamic Routing production mode [ssg: catch-all] should pass params in getStaticProps during client navigation (single interpolated)",
"Dynamic Routing production mode [ssg: catch-all] should pass params in getStaticProps during client navigation (single)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic Routing production mode should allow calling Router.push on mount successfully",
"Dynamic Routing production mode should handle only hash on dynamic route",
"Dynamic Routing production mode should handle only query on dynamic route",
"Dynamic Routing production mode should navigate optional dynamic page",
"Dynamic Routing production mode should navigate optional dynamic page with value",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Dynamic Routing production mode should navigate to a dynamic page successfully",
"Dynamic Routing production mode should navigate to a dynamic page successfully interpolated",
"Dynamic Routing production mode should navigate to a dynamic page successfully interpolated with additional query values",
"Dynamic Routing production mode should navigate to a dynamic page successfully no as",
"Dynamic Routing production mode should navigate to a dynamic page with href with differing query and as correctly",
"Dynamic Routing production mode should navigate to a nested dynamic page successfully",
"Dynamic Routing production mode should navigate to a nested dynamic page successfully interpolated",
"Dynamic Routing production mode should navigate to a nested dynamic page successfully no as",
"Dynamic Routing production mode should navigate with hash to dynamic route with link",
"Dynamic Routing production mode should navigate with hash to dynamic route with router",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic Routing production mode should not error when requesting dynamic page with /api",
"Dynamic Routing production mode should not have any query values when not defined",
"Dynamic Routing production mode should not have placeholder query values for SSS",
"Dynamic Routing production mode should not preload buildManifest for non-auto export dynamic pages",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Dynamic Routing production mode should output a pages-manifest correctly",
"Dynamic Routing production mode should output a routes-manifest correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic Routing production mode should pass params in getInitialProps during SSR",
"Dynamic Routing production mode should pass params in getInitialProps during client navigation",
"Dynamic Routing production mode should prioritize a non-dynamic page",
"Dynamic Routing production mode should prioritize public files over dynamic route",
"Dynamic Routing production mode should render another normal route",
"Dynamic Routing production mode should render dynamic page",
"Dynamic Routing production mode should render nested dynamic page",
"Dynamic Routing production mode should render nested optional dynamic page",
"Dynamic Routing production mode should render normal route",
"Dynamic Routing production mode should render optional dynamic page",
"Dynamic Routing production mode should respond with bad request with invalid encoding",
"Dynamic Routing production mode should scroll to a hash on client-side navigation",
"Dynamic Routing production mode should scroll to a hash on mount",
"Dynamic Routing production mode should serve file from public folder encoded",
"Dynamic Routing production mode should serve file from static folder encoded",
"Dynamic Routing production mode should serve file with %20 from public folder",
"Dynamic Routing production mode should serve file with %20 from static folder",
"Dynamic Routing production mode should serve file with plus from public folder",
"Dynamic Routing production mode should serve file with plus from static folder",
"Dynamic Routing production mode should serve file with space from public folder",
"Dynamic Routing production mode should serve file with space from static folder",
"Dynamic Routing production mode should support long URLs for dynamic routes",
"Dynamic Routing production mode should update dynamic values on mount",
"Dynamic Routing production mode should update with a hash in the URL"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [
fix(ci): exclusion regex now actually works instead of ignoring all tests (#58259)
2023-11-09 21:43:35 +01:00
"Dynamic Routing dev mode should work with HMR correctly",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing production mode should have correct cache entries on prefetch",
"Dynamic Routing production mode should render dynamic route with query"
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
],
"runtimeError": false
},
"test/integration/dynamic-routing/test/middleware.test.js": {
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"passed": [
"Dynamic Routing dev mode [catch all] should not decode slashes (end)",
"Dynamic Routing dev mode [catch all] should not decode slashes (middle)",
"Dynamic Routing dev mode [catch all] should not decode slashes (start)",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Dynamic Routing dev mode [catch all] should not match root on SSR",
"Dynamic Routing dev mode [catch all] should pass param in getInitialProps during SSR",
"Dynamic Routing dev mode [catch all] should pass params in getInitialProps during SSR",
"Dynamic Routing dev mode [catch all] should strip trailing slash",
"Dynamic Routing dev mode [catch-all] should pass params in getInitialProps during client navigation (encoded)",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing dev mode [catch-all] should pass params in getInitialProps during client navigation (multi)",
"Dynamic Routing dev mode [catch-all] should pass params in getInitialProps during client navigation (single)",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Dynamic Routing dev mode [catch-all] shouldn't fail on colon followed by double digits in the path",
"Dynamic Routing dev mode [nested ssg: catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing dev mode [nested ssg: catch all] should pass params in getStaticProps during SSR",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing dev mode [nested ssg: catch-all] should pass params in getStaticProps during client navigation (multi)",
"Dynamic Routing dev mode [nested ssg: catch-all] should pass params in getStaticProps during client navigation (single)",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Dynamic Routing dev mode [predefined ssg: catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing dev mode [predefined ssg: catch all] should pass params in getStaticProps during SSR",
"Dynamic Routing dev mode [predefined ssg: prerendered catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing dev mode [predefined ssg: prerendered catch all] should pass params in getStaticProps during SSR",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing dev mode [ssg: catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing dev mode [ssg: catch all] should pass params in getStaticProps during SSR",
"Dynamic Routing dev mode [ssg: catch-all] should pass params in getStaticProps during client navigation (multi interpolated)",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Dynamic Routing dev mode [ssg: catch-all] should pass params in getStaticProps during client navigation (multi)",
"Dynamic Routing dev mode [ssg: catch-all] should pass params in getStaticProps during client navigation (multi) no as",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing dev mode [ssg: catch-all] should pass params in getStaticProps during client navigation (single interpolated)",
"Dynamic Routing dev mode [ssg: catch-all] should pass params in getStaticProps during client navigation (single)",
"Dynamic Routing dev mode should allow calling Router.push on mount successfully",
"Dynamic Routing dev mode should handle only hash on dynamic route",
"Dynamic Routing dev mode should handle only query on dynamic route",
"Dynamic Routing dev mode should navigate optional dynamic page",
"Dynamic Routing dev mode should navigate optional dynamic page with value",
"Dynamic Routing dev mode should navigate to a dynamic page successfully",
"Dynamic Routing dev mode should navigate to a dynamic page successfully interpolated",
"Dynamic Routing dev mode should navigate to a dynamic page successfully interpolated with additional query values",
"Dynamic Routing dev mode should navigate to a dynamic page successfully no as",
"Dynamic Routing dev mode should navigate to a dynamic page with href with differing query and as correctly",
"Dynamic Routing dev mode should navigate to a nested dynamic page successfully",
"Dynamic Routing dev mode should navigate to a nested dynamic page successfully interpolated",
"Dynamic Routing dev mode should navigate to a nested dynamic page successfully no as",
"Dynamic Routing dev mode should navigate with hash to dynamic route with link",
"Dynamic Routing dev mode should navigate with hash to dynamic route with router",
"Dynamic Routing dev mode should not error when requesting dynamic page with /api",
"Dynamic Routing dev mode should not have any console warnings on initial load",
"Dynamic Routing dev mode should not have any console warnings when navigating to dynamic route",
"Dynamic Routing dev mode should not have any query values when not defined",
"Dynamic Routing dev mode should not have placeholder query values for SSS",
"Dynamic Routing dev mode should not preload buildManifest for non-auto export dynamic pages",
"Dynamic Routing dev mode should pass params in getInitialProps during SSR",
"Dynamic Routing dev mode should pass params in getInitialProps during client navigation",
"Dynamic Routing dev mode should prioritize a non-dynamic page",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Dynamic Routing dev mode should prioritize public files over dynamic route",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing dev mode should render another normal route",
"Dynamic Routing dev mode should render dynamic page",
"Dynamic Routing dev mode should render dynamic route with query",
"Dynamic Routing dev mode should render nested dynamic page",
"Dynamic Routing dev mode should render nested optional dynamic page",
"Dynamic Routing dev mode should render normal route",
"Dynamic Routing dev mode should render optional dynamic page",
"Dynamic Routing dev mode should respond with bad request with invalid encoding",
"Dynamic Routing dev mode should scroll to a hash on client-side navigation",
"Dynamic Routing dev mode should scroll to a hash on mount",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Dynamic Routing dev mode should serve file from public folder encoded",
"Dynamic Routing dev mode should serve file from static folder encoded",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing dev mode should serve file with %20 from public folder",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Dynamic Routing dev mode should serve file with %20 from static folder",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing dev mode should serve file with plus from public folder",
"Dynamic Routing dev mode should serve file with plus from static folder",
"Dynamic Routing dev mode should serve file with space from public folder",
"Dynamic Routing dev mode should serve file with space from static folder",
"Dynamic Routing dev mode should support long URLs for dynamic routes",
"Dynamic Routing dev mode should update dynamic values on mount",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"Dynamic Routing dev mode should update with a hash in the URL",
"Dynamic Routing dev mode should work with HMR correctly"
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
],
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"Dynamic Routing dev mode should not have error after pinging WebSocket",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing production mode [catch all] should not decode slashes (end)",
"Dynamic Routing production mode [catch all] should not decode slashes (middle)",
"Dynamic Routing production mode [catch all] should not decode slashes (start)",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Dynamic Routing production mode [catch all] should not match root on SSR",
"Dynamic Routing production mode [catch all] should pass param in getInitialProps during SSR",
"Dynamic Routing production mode [catch all] should pass params in getInitialProps during SSR",
"Dynamic Routing production mode [catch all] should strip trailing slash",
"Dynamic Routing production mode [catch-all] should pass params in getInitialProps during client navigation (encoded)",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing production mode [catch-all] should pass params in getInitialProps during client navigation (multi)",
"Dynamic Routing production mode [catch-all] should pass params in getInitialProps during client navigation (single)",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Dynamic Routing production mode [catch-all] shouldn't fail on colon followed by double digits in the path",
"Dynamic Routing production mode [nested ssg: catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing production mode [nested ssg: catch all] should pass params in getStaticProps during SSR",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing production mode [nested ssg: catch-all] should pass params in getStaticProps during client navigation (multi)",
"Dynamic Routing production mode [nested ssg: catch-all] should pass params in getStaticProps during client navigation (single)",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Dynamic Routing production mode [predefined ssg: catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing production mode [predefined ssg: catch all] should pass params in getStaticProps during SSR",
"Dynamic Routing production mode [predefined ssg: prerendered catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing production mode [predefined ssg: prerendered catch all] should pass params in getStaticProps during SSR",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing production mode [ssg: catch all] should pass param in getStaticProps during SSR",
"Dynamic Routing production mode [ssg: catch all] should pass params in getStaticProps during SSR",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Dynamic Routing production mode [ssg: catch-all] should pass params in getStaticProps during client navigation (multi interpolated)",
"Dynamic Routing production mode [ssg: catch-all] should pass params in getStaticProps during client navigation (multi)",
"Dynamic Routing production mode [ssg: catch-all] should pass params in getStaticProps during client navigation (multi) no as",
"Dynamic Routing production mode [ssg: catch-all] should pass params in getStaticProps during client navigation (single interpolated)",
"Dynamic Routing production mode [ssg: catch-all] should pass params in getStaticProps during client navigation (single)",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing production mode should allow calling Router.push on mount successfully",
"Dynamic Routing production mode should handle only hash on dynamic route",
"Dynamic Routing production mode should handle only query on dynamic route",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Dynamic Routing production mode should have correct cache entries on prefetch",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing production mode should navigate optional dynamic page",
"Dynamic Routing production mode should navigate optional dynamic page with value",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Dynamic Routing production mode should navigate to a dynamic page successfully",
"Dynamic Routing production mode should navigate to a dynamic page successfully interpolated",
"Dynamic Routing production mode should navigate to a dynamic page successfully interpolated with additional query values",
"Dynamic Routing production mode should navigate to a dynamic page successfully no as",
"Dynamic Routing production mode should navigate to a dynamic page with href with differing query and as correctly",
"Dynamic Routing production mode should navigate to a nested dynamic page successfully",
"Dynamic Routing production mode should navigate to a nested dynamic page successfully interpolated",
"Dynamic Routing production mode should navigate to a nested dynamic page successfully no as",
"Dynamic Routing production mode should navigate with hash to dynamic route with link",
"Dynamic Routing production mode should navigate with hash to dynamic route with router",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing production mode should not error when requesting dynamic page with /api",
"Dynamic Routing production mode should not have any query values when not defined",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Dynamic Routing production mode should not have placeholder query values for SSS",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing production mode should not preload buildManifest for non-auto export dynamic pages",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Dynamic Routing production mode should output a pages-manifest correctly",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing production mode should pass params in getInitialProps during SSR",
"Dynamic Routing production mode should pass params in getInitialProps during client navigation",
"Dynamic Routing production mode should prioritize a non-dynamic page",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Dynamic Routing production mode should prioritize public files over dynamic route",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing production mode should render another normal route",
"Dynamic Routing production mode should render dynamic page",
"Dynamic Routing production mode should render dynamic route with query",
"Dynamic Routing production mode should render nested dynamic page",
"Dynamic Routing production mode should render nested optional dynamic page",
"Dynamic Routing production mode should render normal route",
"Dynamic Routing production mode should render optional dynamic page",
"Dynamic Routing production mode should respond with bad request with invalid encoding",
"Dynamic Routing production mode should scroll to a hash on client-side navigation",
"Dynamic Routing production mode should scroll to a hash on mount",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Dynamic Routing production mode should serve file from public folder encoded",
"Dynamic Routing production mode should serve file from static folder encoded",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing production mode should serve file with %20 from public folder",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"Dynamic Routing production mode should serve file with %20 from static folder",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Dynamic Routing production mode should serve file with plus from public folder",
"Dynamic Routing production mode should serve file with plus from static folder",
"Dynamic Routing production mode should serve file with space from public folder",
"Dynamic Routing production mode should serve file with space from static folder",
"Dynamic Routing production mode should support long URLs for dynamic routes",
"Dynamic Routing production mode should update dynamic values on mount",
"Dynamic Routing production mode should update with a hash in the URL"
],
"flakey": [
"Dynamic Routing dev mode should resolve dynamic route href for page added later",
"Dynamic Routing production mode should output a routes-manifest correctly"
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/edge-runtime-configurable-guards/test/index.test.js": {
"passed": [
"Edge runtime configurable guards Edge API with use of Function as a type does not warn in dev at runtime",
"Edge runtime configurable guards Middleware with use of Function as a type does not warn in dev at runtime"
],
"failed": [
"Edge runtime configurable guards Edge API using lib with allowed, used dynamic code still warns in dev at runtime",
"Edge runtime configurable guards Edge API using lib with unallowed, used dynamic code warns in dev at runtime",
"Edge runtime configurable guards Edge API with allowed, used dynamic code still warns in dev at runtime",
"Edge runtime configurable guards Middleware using lib with allowed, used dynamic code still warns in dev at runtime",
"Edge runtime configurable guards Middleware using lib with unallowed, used dynamic code warns in dev at runtime",
"Edge runtime configurable guards Middleware with allowed, used dynamic code still warns in dev at runtime",
"Edge runtime configurable guards Multiple functions with different configurations warns in dev for allowed code",
"Edge runtime configurable guards Multiple functions with different configurations warns in dev for unallowed code"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Edge runtime configurable guards Edge API using lib with allowed, unused dynamic code production mode build and does not warn at runtime",
"Edge runtime configurable guards Edge API using lib with unallowed, used dynamic code production mode fails to build because of dynamic code evaluation",
"Edge runtime configurable guards Edge API with allowed, unused dynamic code production mode build and does not warn at runtime",
"Edge runtime configurable guards Edge API with use of Function as a type production mode build and does not warn at runtime",
"Edge runtime configurable guards Middleware using lib with allowed, unused dynamic code production mode build and does not warn at runtime",
"Edge runtime configurable guards Middleware using lib with unallowed, used dynamic code production mode fails to build because of dynamic code evaluation",
"Edge runtime configurable guards Middleware with allowed, unused dynamic code production mode build and does not warn at runtime",
"Edge runtime configurable guards Middleware with use of Function as a type production mode build and does not warn at runtime",
"Edge runtime configurable guards Multiple functions with different configurations production mode fails to build because of unallowed code"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/edge-runtime-dynamic-code/test/index.test.js": {
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Edge route usage of dynamic code evaluation dev mode does not show a warning when running WebAssembly.instantiate with a module parameter",
"Edge route usage of dynamic code evaluation dev mode does not show warning when no code uses eval",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"Middleware usage of dynamic code evaluation dev mode does not show a warning when running WebAssembly.instantiate with a module parameter",
"Middleware usage of dynamic code evaluation dev mode does not show warning when no code uses eval",
"Page using eval in dev mode does issue dynamic code evaluation warnings"
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Edge route usage of dynamic code evaluation dev mode shows a warning when running WebAssembly.compile",
"Edge route usage of dynamic code evaluation dev mode shows a warning when running WebAssembly.instantiate with a buffer parameter",
"Edge route usage of dynamic code evaluation dev mode shows a warning when running code with eval",
"Middleware usage of dynamic code evaluation dev mode shows a warning when running WebAssembly.compile",
"Middleware usage of dynamic code evaluation dev mode shows a warning when running WebAssembly.instantiate with a buffer parameter",
Update Turbopack test manifest (#60306) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2024-01-07 09:51:32 +01:00
"Middleware usage of dynamic code evaluation dev mode shows a warning when running code with eval"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"Edge route usage of dynamic code evaluation production mode should have middleware warning during build",
"Middleware usage of dynamic code evaluation production mode should have middleware warning during build"
],
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/edge-runtime-module-errors/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Edge runtime code with imports Edge API importing vanilla 3rd party module does not throw in dev at runtime",
"Edge runtime code with imports Edge API using Buffer polyfill does not throw in dev at runtime",
"Edge runtime code with imports Middleware importing vanilla 3rd party module does not throw in dev at runtime",
"Edge runtime code with imports Middleware using Buffer polyfill does not throw in dev at runtime"
],
"failed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Edge runtime code with imports Edge API dynamically importing node.js module development mode throws unsupported module error in dev at runtime and highlights the faulty line",
"Edge runtime code with imports Edge API dynamically importing node.js module in a lib development mode throws unsupported module error in dev at runtime and highlights the faulty line",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Edge runtime code with imports Edge API statically importing 3rd party module throws not-found module error in dev at runtime and highlights the faulty line",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Edge runtime code with imports Middleware dynamically importing node.js module development mode throws unsupported module error in dev at runtime and highlights the faulty line",
"Edge runtime code with imports Middleware dynamically importing node.js module in a lib development mode throws unsupported module error in dev at runtime and highlights the faulty line",
"Edge runtime code with imports Middleware statically importing 3rd party module throws not-found module error in dev at runtime and highlights the faulty line"
],
"pending": [
"Edge runtime code with imports Edge API dynamically importing node.js module in a lib production mode throws unsupported module error in production at runtime and prints error on logs",
"Edge runtime code with imports Edge API dynamically importing node.js module production mode throws unsupported module error in production at runtime and prints error on logs",
"Edge runtime code with imports Edge API importing vanilla 3rd party module production mode does not throw in production at runtime",
"Edge runtime code with imports Edge API statically importing 3rd party module production mode does not build and reports",
"Edge runtime code with imports Edge API using Buffer polyfill production mode does not throw in production at runtime",
"Edge runtime code with imports Middleware dynamically importing node.js module in a lib production mode throws unsupported module error in production at runtime and prints error on logs",
"Edge runtime code with imports Middleware dynamically importing node.js module production mode throws unsupported module error in production at runtime and prints error on logs",
"Edge runtime code with imports Middleware importing vanilla 3rd party module production mode does not throw in production at runtime",
"Edge runtime code with imports Middleware statically importing 3rd party module production mode does not build and reports",
"Edge runtime code with imports Middleware using Buffer polyfill production mode does not throw in production at runtime"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/edge-runtime-module-errors/test/module-imports.test.js": {
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"passed": [
"Edge runtime code with imports Edge API importing unused node.js module does not throw in dev at runtime"
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [
"Edge runtime code with imports Edge API dynamically importing 3rd party module throws not-found module error in dev at runtime and highlights the faulty line",
"Edge runtime code with imports Edge API importing unused 3rd party module throws not-found module error in dev at runtime and highlights the faulty line",
"Edge runtime code with imports Edge API statically importing node.js module throws unsupported module error in dev at runtime and highlights the faulty line",
"Edge runtime code with imports Middleware dynamically importing 3rd party module throws not-found module error in dev at runtime and highlights the faulty line",
"Edge runtime code with imports Middleware importing unused 3rd party module throws not-found module error in dev at runtime and highlights the faulty line",
Turbopack: Use structured styled text in issue descriptions (#58156) Requires vercel/turbo#6388 This uses the structure implemented in vercel/turbo#6388 to support formatted text when reporting. Right now only the `Line` and basic `String` cases are handled.
2023-11-15 23:33:14 +01:00
"Edge runtime code with imports Middleware importing unused node.js module does not throw in dev at runtime",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Edge runtime code with imports Middleware statically importing node.js module throws unsupported module error in dev at runtime and highlights the faulty line"
],
"pending": [
"Edge runtime code with imports Edge API dynamically importing 3rd party module production mode does not build and reports module not found error",
"Edge runtime code with imports Edge API importing unused 3rd party module production mode does not build and reports module not found error",
"Edge runtime code with imports Edge API importing unused node.js module production mode does not throw in production at runtime",
"Edge runtime code with imports Edge API statically importing node.js module production mode throws unsupported module error in production at runtime and prints error on logs",
"Edge runtime code with imports Middleware dynamically importing 3rd party module production mode does not build and reports module not found error",
"Edge runtime code with imports Middleware importing unused 3rd party module production mode does not build and reports module not found error",
"Edge runtime code with imports Middleware importing unused node.js module production mode does not throw in production at runtime",
"Edge runtime code with imports Middleware statically importing node.js module production mode throws unsupported module error in production at runtime and prints error on logs"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/edge-runtime-response-error/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Edge runtime code with imports test error if response is not Response type Edge API dev test Response",
"Edge runtime code with imports test error if response is not Response type Middleware dev test Response"
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Edge runtime code with imports test error if response is not Response type production mode Edge API build test Response",
"Edge runtime code with imports test error if response is not Response type production mode Middleware build test Response"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/edge-runtime-streaming-error/test/index.test.ts": {
"passed": ["dev mode logs the error correctly"],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"failed": [],
"pending": ["production mode logs the error correctly"],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/edge-runtime-with-node.js-apis/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Edge route using Node.js API dev mode does not throw on using process.arch",
"Edge route using Node.js API dev mode does not throw on using process.version",
"Edge route using Node.js API dev mode throws error when using BroadcastChannel",
"Edge route using Node.js API dev mode throws error when using ByteLengthQueuingStrategy",
"Edge route using Node.js API dev mode throws error when using CompressionStream",
"Edge route using Node.js API dev mode throws error when using CountQueuingStrategy",
"Edge route using Node.js API dev mode throws error when using DecompressionStream",
"Edge route using Node.js API dev mode throws error when using DomException",
"Edge route using Node.js API dev mode throws error when using MessageChannel",
"Edge route using Node.js API dev mode throws error when using MessageEvent",
"Edge route using Node.js API dev mode throws error when using MessagePort",
"Edge route using Node.js API dev mode throws error when using ReadableByteStreamController",
"Edge route using Node.js API dev mode throws error when using ReadableStreamBYOBRequest",
"Edge route using Node.js API dev mode throws error when using ReadableStreamDefaultController",
"Edge route using Node.js API dev mode throws error when using TransformStreamDefaultController",
"Edge route using Node.js API dev mode throws error when using WritableStreamDefaultController",
"Edge route using Node.js API dev mode throws error when using clearImmediate",
"Edge route using Node.js API dev mode throws error when using process.cpuUsage",
"Edge route using Node.js API dev mode throws error when using process.cwd",
"Edge route using Node.js API dev mode throws error when using process.getuid",
"Edge route using Node.js API dev mode throws error when using setImmediate",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"Middleware using Node.js API dev mode does not throw on using process.arch",
"Middleware using Node.js API dev mode does not throw on using process.version",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Middleware using Node.js API dev mode throws error when using BroadcastChannel",
"Middleware using Node.js API dev mode throws error when using ByteLengthQueuingStrategy",
"Middleware using Node.js API dev mode throws error when using CompressionStream",
"Middleware using Node.js API dev mode throws error when using CountQueuingStrategy",
"Middleware using Node.js API dev mode throws error when using DecompressionStream",
"Middleware using Node.js API dev mode throws error when using DomException",
"Middleware using Node.js API dev mode throws error when using MessageChannel",
"Middleware using Node.js API dev mode throws error when using MessageEvent",
"Middleware using Node.js API dev mode throws error when using MessagePort",
"Middleware using Node.js API dev mode throws error when using ReadableByteStreamController",
"Middleware using Node.js API dev mode throws error when using ReadableStreamBYOBRequest",
"Middleware using Node.js API dev mode throws error when using ReadableStreamDefaultController",
"Middleware using Node.js API dev mode throws error when using TransformStreamDefaultController",
"Middleware using Node.js API dev mode throws error when using WritableStreamDefaultController",
"Middleware using Node.js API dev mode throws error when using clearImmediate",
"Middleware using Node.js API dev mode throws error when using process.cpuUsage",
"Middleware using Node.js API dev mode throws error when using process.cwd",
"Middleware using Node.js API dev mode throws error when using process.getuid",
"Middleware using Node.js API dev mode throws error when using setImmediate"
],
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Edge route using Node.js API production mode does not warn on using process.arch",
"Edge route using Node.js API production mode does not warn on using process.version",
"Edge route using Node.js API production mode warns for BroadcastChannel during build",
"Edge route using Node.js API production mode warns for ByteLengthQueuingStrategy during build",
"Edge route using Node.js API production mode warns for CompressionStream during build",
"Edge route using Node.js API production mode warns for CountQueuingStrategy during build",
"Edge route using Node.js API production mode warns for DecompressionStream during build",
"Edge route using Node.js API production mode warns for DomException during build",
"Edge route using Node.js API production mode warns for MessageChannel during build",
"Edge route using Node.js API production mode warns for MessageEvent during build",
"Edge route using Node.js API production mode warns for MessagePort during build",
"Edge route using Node.js API production mode warns for ReadableByteStreamController during build",
"Edge route using Node.js API production mode warns for ReadableStreamBYOBRequest during build",
"Edge route using Node.js API production mode warns for ReadableStreamDefaultController during build",
"Edge route using Node.js API production mode warns for TransformStreamDefaultController during build",
"Edge route using Node.js API production mode warns for WritableStreamDefaultController during build",
"Edge route using Node.js API production mode warns for clearImmediate during build",
"Edge route using Node.js API production mode warns for process.cpuUsage during build",
"Edge route using Node.js API production mode warns for process.cwd during build",
"Edge route using Node.js API production mode warns for process.getuid during build",
"Edge route using Node.js API production mode warns for setImmediate during build",
"Middleware using Node.js API production mode does not warn on using process.arch",
"Middleware using Node.js API production mode does not warn on using process.version",
"Middleware using Node.js API production mode warns for BroadcastChannel during build",
"Middleware using Node.js API production mode warns for ByteLengthQueuingStrategy during build",
"Middleware using Node.js API production mode warns for CompressionStream during build",
"Middleware using Node.js API production mode warns for CountQueuingStrategy during build",
"Middleware using Node.js API production mode warns for DecompressionStream during build",
"Middleware using Node.js API production mode warns for DomException during build",
"Middleware using Node.js API production mode warns for MessageChannel during build",
"Middleware using Node.js API production mode warns for MessageEvent during build",
"Middleware using Node.js API production mode warns for MessagePort during build",
"Middleware using Node.js API production mode warns for ReadableByteStreamController during build",
"Middleware using Node.js API production mode warns for ReadableStreamBYOBRequest during build",
"Middleware using Node.js API production mode warns for ReadableStreamDefaultController during build",
"Middleware using Node.js API production mode warns for TransformStreamDefaultController during build",
"Middleware using Node.js API production mode warns for WritableStreamDefaultController during build",
"Middleware using Node.js API production mode warns for clearImmediate during build",
"Middleware using Node.js API production mode warns for process.cpuUsage during build",
"Middleware using Node.js API production mode warns for process.cwd during build",
"Middleware using Node.js API production mode warns for process.getuid during build",
"Middleware using Node.js API production mode warns for setImmediate during build"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/empty-object-getInitialProps/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Empty Project It should not show empty object warning for page without `getInitialProps`",
"Empty Project It should show empty object warning on SSR",
"Empty Project should show empty object warning during client transition"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/empty-project/test/index.test.js": {
"passed": ["Empty Project Should not time out and return 404"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/env-config/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Env Config dev mode should have process environment override .env",
"Env Config dev mode should load env from .env",
"Env Config dev mode should provide env correctly for API routes",
"Env Config dev mode should provide env correctly for SSR",
"Env Config dev mode should provide env for SSG",
"Env Config dev mode should provide global env to next.config.js",
"Env Config dev mode with hot reload should have process environment override .env",
"Env Config dev mode with hot reload should have updated runtime values after change",
"Env Config dev mode with hot reload should load env from .env",
"Env Config dev mode with hot reload should provide global env to next.config.js",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"Env Config dev mode with hot reload should trigger HMR correctly when NEXT_PUBLIC_ env is changed",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Env Config test environment should provide env correctly for API routes",
"Env Config test environment should provide global env to next.config.js"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Env Config dev mode should inline global values during build",
"Env Config dev mode with hot reload should inline global values during build",
"Env Config test environment should have process environment override .env",
"Env Config test environment should inline global values during build",
"Env Config test environment should load env from .env",
"Env Config test environment should provide env correctly for SSR",
"Env Config test environment should provide env for SSG"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"Env Config production mode should have process environment override .env",
"Env Config production mode should inline global values during build",
"Env Config production mode should load env from .env",
"Env Config production mode should provide env correctly for API routes",
"Env Config production mode should provide env correctly for SSR",
"Env Config production mode should provide env for SSG",
"Env Config production mode should provide global env to next.config.js"
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"flakey": [
"Env Config dev mode with hot reload should provide env correctly for API routes",
"Env Config dev mode with hot reload should provide env correctly for SSR",
"Env Config dev mode with hot reload should provide env for SSG"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"runtimeError": false
},
"test/integration/error-in-error/test/index.test.js": {
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Handles an Error in _error production mode Handles error during SSR",
"Handles an Error in _error production mode Handles error during client transition"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/error-load-fail/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Failing to load _error production mode handles failing to load _error correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/error-plugin-stack-overflow/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Reports stack trace when webpack plugin stack overflows shows details in next build"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/errors-on-output-to-public/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Errors on output to public production mode Throws error when `distDir` is set to public",
"Errors on output to public production mode Throws error when export out dir is public"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/errors-on-output-to-static/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Errors on output to static production mode Throws error when export out dir is static"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/eslint/test/lint-cache.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"cache with content strategy is different from the one with default strategy",
"eslint caching is disabled with the --no-cache flag",
"eslint caching is enabled by default",
"the --cache-location flag allows the user to define a separate cache location",
"the default eslint cache lives in the user defined build directory",
"the default eslint caching strategy is metadata"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/eslint/test/next-build.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"Next Build production mode base directories are linted by default during builds",
"Next Build production mode custom directories",
"Next Build production mode empty directories do not fail the build",
"Next Build production mode eslint cache lives in the user defined build directory",
"Next Build production mode eslint caching is enabled",
"Next Build production mode eslint ignored directories do not fail the build",
"Next Build production mode first time setup",
"Next Build production mode ignore during builds",
"Next Build production mode invalid older eslint version",
"Next Build production mode missing Next.js plugin",
"Next Build production mode shows warnings and errors"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/eslint/test/next-lint.test.js": {
"passed": [
"Next Lint First Time Setup creates .eslintrc.json file with a default configuration",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Next Lint First Time Setup installs eslint and eslint-config-next as devDependencies if missing with npm",
"Next Lint First Time Setup installs eslint and eslint-config-next as devDependencies if missing with pnpm",
"Next Lint First Time Setup installs eslint and eslint-config-next as devDependencies if missing with yarn",
"Next Lint First Time Setup show a prompt to set up ESLint if no configuration detected",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Next Lint First Time Setup shows a successful message when completed",
"Next Lint base directories are linted by default",
"Next Lint custom directories",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Next Lint don't create .eslintrc file if package.json has eslintConfig field",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Next Lint file flag can selectively lint only a single file",
"Next Lint file flag can selectively lints multiple files",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Next Lint format flag supports additional user-defined formats",
"Next Lint lint files with cjs and mjs file extension",
"Next Lint max warnings flag does not error when warnings do not exceed threshold",
"Next Lint max warnings flag errors when warnings exceed threshold",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Next Lint output flag create a file respecting the chosen format",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Next Lint quiet flag suppresses warnings and only reports errors",
"Next Lint should add relative path for dist types in tsconfig.json when app dir exist",
"Next Lint should generate next-env.d.ts before lint command",
"Next Lint should not generate next-env.d.ts without typescript",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Next Lint show error message when the file path is a directory",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Next Lint shows warnings and errors",
"Next Lint shows warnings and errors when extending plugin core-web-vitals config",
"Next Lint shows warnings and errors when extending plugin recommended config",
"Next Lint shows warnings and errors with next/core-web-vitals config",
"Next Lint success message when no warnings or errors"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/export-404/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Export with a page named 404.js production mode should export a custom 404.html instead of default 404.html",
"Static 404 Export production mode export 404.html and 404/index.html when trailingSlash: true",
"Static 404 Export production mode only export 404.html when trailingSlash: false"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/export-default-map/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Export with default map production mode should export an amp only page to clean path",
"Export with default map production mode should export hybrid amp page correctly",
"Export with default map production mode should export hybrid index amp page correctly",
"Export with default map production mode should export nested hybrid amp page correctly",
"Export with default map production mode should export nested hybrid amp page correctly with folder",
"Export with default map production mode should export with folder that has dot in name"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/export-dynamic-pages/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Export Dynamic Pages production mode should hydrate with correct asPath",
"Export Dynamic Pages production mode should of exported with correct asPath"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/export-fallback-true-error/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"Export error for fallback: true production mode should build successfully"
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/export-getInitialProps-warn/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Export with getInitialProps production mode should show warning with next export"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/export-image-default/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"Export with default loader next/image component production mode should error during next build"
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/export-image-loader-legacy/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Export with cloudinary loader next/legacy/image component production mode should build successfully",
"Export with cloudinary loader next/legacy/image component production mode should contain img element in html output",
"Export with custom loader config but no loader prop on next/legacy/image production mode should fail build",
"Export with custom loader next/legacy/image component production mode should build successfully",
"Export with custom loader next/legacy/image component production mode should contain img element with same src in html output",
"Export with unoptimized next/legacy/image component production mode should build successfully",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"Export with unoptimized next/legacy/image component production mode should contain img element with same src in html output"
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/export-image-loader/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"Export with cloudinary loader next/image component production mode should build successfully",
"Export with cloudinary loader next/image component production mode should contain img element in html output",
"Export with custom loader config but no loader prop on next/image production mode should fail build",
"Export with custom loader next/image component production mode should build successfully",
"Export with custom loader next/image component production mode should contain img element with same src in html output",
"Export with loaderFile config next/image component production mode should build successfully",
"Export with loaderFile config next/image component production mode should contain img element with same src in html output",
"Export with unoptimized next/image component production mode should build successfully",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"Export with unoptimized next/image component production mode should contain img element with same src in html output"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/export-index-not-found-gsp/test/index.test.ts": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"Export index page with `notFound: true` in `getStaticProps` production mode should build successfully"
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/export-intent/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"Application Export Intent Output Bad Export production mode should build and export",
"Application Export Intent Output Bad Export production mode should have the expected outputs for export",
"Application Export Intent Output Custom Export production mode should build and export",
"Application Export Intent Output Custom Export production mode should have the expected outputs for export",
"Application Export Intent Output Custom Out production mode should build and export",
"Application Export Intent Output Custom Out production mode should have the expected outputs for export",
"Application Export Intent Output No Export production mode should build and clean up",
"Application Export Intent Output No Export production mode should build and not export",
"Application Export Intent Output No Export production mode should have the expected outputs for export",
"Application Export Intent Output production mode Default Export should build and export",
"Application Export Intent Output production mode Default Export should have the expected outputs for export"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/export-subfolders/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Export config#exportTrailingSlash set to false production mode should export pages as [filename].html instead of [filename]/index.html"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/externals-esm-loose/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Handle ESM externals with esmExternals: 'loose' production mode should render the ssg page",
"Handle ESM externals with esmExternals: 'loose' production mode should render the ssr page",
"Handle ESM externals with esmExternals: 'loose' production mode should render the static page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/externals-esm/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Handle ESM externals with esmExternals: true production mode should render the ssg page",
"Handle ESM externals with esmExternals: true production mode should render the ssr page",
"Handle ESM externals with esmExternals: true production mode should render the static page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"test/integration/externals-pages-bundle/test/externals.test.js": {
"passed": [
"default should use externals for unvendored node_modules reachable from the project"
],
"failed": [],
"pending": [],
"flakey": [],
"runtimeError": false
},
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"test/integration/externals-pages-bundle/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"bundle pages externals with config.experimental.bundlePagesExternals production mode should have no externals with the config set",
"bundle pages externals with config.experimental.bundlePagesExternals production mode should respect the serverComponentsExternals config"
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/fallback-false-rewrite/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"fallback: false rewrite dev mode should behave properly when accessing the dynamic param directly",
"fallback: false rewrite dev mode should not rewrite for path from fallback: false SSR",
"fallback: false rewrite dev mode should not rewrite for path from fallback: false client",
"fallback: false rewrite dev mode should rewrite correctly for path above fallback: false SSR",
"fallback: false rewrite dev mode should rewrite correctly for path above fallback: false client",
"fallback: false rewrite dev mode should rewrite correctly for path at same level as fallback: false SSR",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"fallback: false rewrite dev mode should rewrite correctly for path at same level as fallback: false client"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"fallback: false rewrite production mode should behave properly when accessing the dynamic param directly",
"fallback: false rewrite production mode should not rewrite for path from fallback: false SSR",
"fallback: false rewrite production mode should not rewrite for path from fallback: false client",
"fallback: false rewrite production mode should rewrite correctly for path above fallback: false SSR",
"fallback: false rewrite production mode should rewrite correctly for path above fallback: false client",
"fallback: false rewrite production mode should rewrite correctly for path at same level as fallback: false SSR",
"fallback: false rewrite production mode should rewrite correctly for path at same level as fallback: false client"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/fallback-modules/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Fallback Modules production mode Crypto Application should not include crypto"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/fallback-route-params/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Fallback Dynamic Route Params dev mode should have correct fallback query (hydration)",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Fallback Dynamic Route Params dev mode should have correct fallback query (skeleton)"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Fallback Dynamic Route Params production mode should have correct fallback query (hydration)",
"Fallback Dynamic Route Params production mode should have correct fallback query (skeleton)"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/fetch-polyfill-ky-universal/test/index.test.js": {
"passed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Fetch polyfill with ky-universal development mode includes polyfilled fetch when using getInitialProps",
"Fetch polyfill with ky-universal development mode includes polyfilled fetch when using getServerSideProps",
"Fetch polyfill with ky-universal development mode includes polyfilled fetch when using getStaticProps"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Fetch polyfill with ky-universal production mode includes polyfilled fetch when using getInitialProps",
"Fetch polyfill with ky-universal production mode includes polyfilled fetch when using getServerSideProps",
"Fetch polyfill with ky-universal production mode includes polyfilled fetch when using getStaticProps"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/fetch-polyfill/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Fetch polyfill development mode includes polyfilled fetch when using API routes",
"Fetch polyfill development mode includes polyfilled fetch when using getInitialProps",
"Fetch polyfill development mode includes polyfilled fetch when using getServerSideProps",
"Fetch polyfill development mode includes polyfilled fetch when using getStaticPaths",
"Fetch polyfill development mode includes polyfilled fetch when using getStaticProps"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Fetch polyfill production mode includes polyfilled fetch when using API routes",
"Fetch polyfill production mode includes polyfilled fetch when using getInitialProps",
"Fetch polyfill production mode includes polyfilled fetch when using getServerSideProps",
"Fetch polyfill production mode includes polyfilled fetch when using getStaticPaths",
"Fetch polyfill production mode includes polyfilled fetch when using getStaticProps"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/file-serving/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65/%%32%65%%32%65/test-file.txt",
"File Serving dev mode should prevent traversing with /%%32%65%%32%65/test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%252f%252e%252e%252f%252e%252e%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%252f%252e%252e%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%255c%252e%252e%255c%252e%252e%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%255c%252e%252e%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e/%252e%252e/%252e%252e/%252e%252e/test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e/%252e%252e/%252e%252e/test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e/%252e%252e/test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e/test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e\\%252e%252e\\%252e%252e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e\\%252e%252e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%252e%252e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e/%2e%2e/%2e%2e/%2e%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e/%2e%2e/%2e%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e/%2e%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e\\%2e%2e\\%2e%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e\\%2e%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%2e%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e/%c0%2e%c0%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e\\%c0%2e%c0%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%2e%c0%2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae/%c0%ae%c0%ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae/test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae\\%c0%ae%c0%ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%c0%ae%c0%ae\\test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2215%uff0e%uff0e%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2216%uff0e%uff0e%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e/%uff0e%uff0e/test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e/test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e\\%uff0e%uff0e\\test-file.txt",
"File Serving dev mode should prevent traversing with /%uff0e%uff0e\\test-file.txt",
"File Serving dev mode should prevent traversing with /..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /..%%32%66..%%32%66..%%32%66..%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /..%%32%66..%%32%66..%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /..%%32%66..%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /..%%32%66test-file.txt",
"File Serving dev mode should prevent traversing with /..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /..%%35%63..%%35%63..%%35%63..%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /..%%35%63..%%35%63..%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /..%%35%63..%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /..%%35%63test-file.txt",
"File Serving dev mode should prevent traversing with /..%252f..%252f..%252f..%252f..%252f..%252f..%252f..%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%252f..%252f..%252f..%252f..%252f..%252f..%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%252f..%252f..%252f..%252f..%252f..%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%252f..%252f..%252f..%252f..%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%252f..%252f..%252f..%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%252f..%252f..%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%252f..%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%252ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%255c..%255c..%255c..%255c..%255c..%255c..%255c..%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%255c..%255c..%255c..%255c..%255c..%255c..%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%255c..%255c..%255c..%255c..%255c..%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%255c..%255c..%255c..%255c..%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%255c..%255c..%255c..%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%255c..%255c..%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%255c..%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%255ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c0%25af..%25c0%25af..%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c0%25af..%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c0%25aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c1%259c..%25c1%259c..%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c1%259c..%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%25c1%259ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%2f..%2f..%2f..%2f..%2f..%2f..%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%2f..%2f..%2f..%2f..%2f..%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%2f..%2f..%2f..%2f..%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%2f..%2f..%2f..%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%2f..%2f..%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%2f..%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%5c..%5c..%5c..%5c..%5c..%5c..%5c..%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%5c..%5c..%5c..%5c..%5c..%5c..%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%5c..%5c..%5c..%5c..%5c..%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%5c..%5c..%5c..%5c..%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%5c..%5c..%5c..%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%5c..%5c..%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%5c..%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%2f..%c0%2f..%c0%2f..%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%2f..%c0%2f..%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%2f..%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%5c..%c0%5c..%c0%5c..%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%5c..%c0%5c..%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%5c..%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%af..%c0%af..%c0%af..%c0%af..%c0%af..%c0%af..%c0%af..%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%af..%c0%af..%c0%af..%c0%af..%c0%af..%c0%af..%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%af..%c0%af..%c0%af..%c0%af..%c0%af..%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%af..%c0%af..%c0%af..%c0%af..%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%af..%c0%af..%c0%af..%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%af..%c0%af..%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%af..%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c0%aftest-file.txt",
"File Serving dev mode should prevent traversing with /..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c1%9c..%c1%9c..%c1%9c..%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c1%9c..%c1%9c..%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c1%9c..%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%c1%9ctest-file.txt",
"File Serving dev mode should prevent traversing with /..%u2215..%u2215..%u2215..%u2215..%u2215..%u2215..%u2215..%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /..%u2215..%u2215..%u2215..%u2215..%u2215..%u2215..%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /..%u2215..%u2215..%u2215..%u2215..%u2215..%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /..%u2215..%u2215..%u2215..%u2215..%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /..%u2215..%u2215..%u2215..%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /..%u2215..%u2215..%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /..%u2215..%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /..%u2215test-file.txt",
"File Serving dev mode should prevent traversing with /..%u2216..%u2216..%u2216..%u2216..%u2216..%u2216..%u2216..%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /..%u2216..%u2216..%u2216..%u2216..%u2216..%u2216..%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /..%u2216..%u2216..%u2216..%u2216..%u2216..%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /..%u2216..%u2216..%u2216..%u2216..%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /..%u2216..%u2216..%u2216..%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /..%u2216..%u2216..%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /..%u2216..%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /..%u2216test-file.txt",
"File Serving dev mode should prevent traversing with /..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8test-file.txt",
"File Serving dev mode should prevent traversing with /..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8test-file.txt",
"File Serving dev mode should prevent traversing with /..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8test-file.txt",
"File Serving dev mode should prevent traversing with /..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8test-file.txt",
"File Serving dev mode should prevent traversing with /..%uEFC8..%uEFC8..%uEFC8..%uEFC8test-file.txt",
"File Serving dev mode should prevent traversing with /..%uEFC8..%uEFC8..%uEFC8test-file.txt",
"File Serving dev mode should prevent traversing with /..%uEFC8..%uEFC8test-file.txt",
"File Serving dev mode should prevent traversing with /..%uEFC8test-file.txt",
"File Serving dev mode should prevent traversing with /..%uF025..%uF025..%uF025..%uF025..%uF025..%uF025..%uF025..%uF025test-file.txt",
"File Serving dev mode should prevent traversing with /..%uF025..%uF025..%uF025..%uF025..%uF025..%uF025..%uF025test-file.txt",
"File Serving dev mode should prevent traversing with /..%uF025..%uF025..%uF025..%uF025..%uF025..%uF025test-file.txt",
"File Serving dev mode should prevent traversing with /..%uF025..%uF025..%uF025..%uF025..%uF025test-file.txt",
"File Serving dev mode should prevent traversing with /..%uF025..%uF025..%uF025..%uF025test-file.txt",
"File Serving dev mode should prevent traversing with /..%uF025..%uF025..%uF025test-file.txt",
"File Serving dev mode should prevent traversing with /..%uF025..%uF025test-file.txt",
"File Serving dev mode should prevent traversing with /..%uF025test-file.txt",
"File Serving dev mode should prevent traversing with /........................................................................../../../../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /........................................................................../../../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /........................................................................../../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /........................................................................../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /........................................................................../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /........................................................................../../../test-file.txt",
"File Serving dev mode should prevent traversing with /........................................................................../../test-file.txt",
"File Serving dev mode should prevent traversing with /........................................................................../test-file.txt",
"File Serving dev mode should prevent traversing with /..........................................................................\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..........................................................................\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..........................................................................\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..........................................................................\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..........................................................................\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..........................................................................\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..........................................................................\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..........................................................................\\test-file.txt",
"File Serving dev mode should prevent traversing with /..../..../..../..../..../..../..../..../test-file.txt",
"File Serving dev mode should prevent traversing with /..../..../..../..../..../..../..../test-file.txt",
"File Serving dev mode should prevent traversing with /..../..../..../..../..../..../test-file.txt",
"File Serving dev mode should prevent traversing with /..../..../..../..../..../test-file.txt",
"File Serving dev mode should prevent traversing with /..../..../..../..../test-file.txt",
"File Serving dev mode should prevent traversing with /..../..../..../test-file.txt",
"File Serving dev mode should prevent traversing with /..../..../test-file.txt",
"File Serving dev mode should prevent traversing with /..../test-file.txt",
"File Serving dev mode should prevent traversing with /....\\....\\....\\....\\....\\....\\....\\....\\test-file.txt",
"File Serving dev mode should prevent traversing with /....\\....\\....\\....\\....\\....\\....\\test-file.txt",
"File Serving dev mode should prevent traversing with /....\\....\\....\\....\\....\\....\\test-file.txt",
"File Serving dev mode should prevent traversing with /....\\....\\....\\....\\....\\test-file.txt",
"File Serving dev mode should prevent traversing with /....\\....\\....\\....\\test-file.txt",
"File Serving dev mode should prevent traversing with /....\\....\\....\\test-file.txt",
"File Serving dev mode should prevent traversing with /....\\....\\test-file.txt",
"File Serving dev mode should prevent traversing with /....\\test-file.txt",
"File Serving dev mode should prevent traversing with /.../.../.../.../.../.../.../.../test-file.txt",
"File Serving dev mode should prevent traversing with /.../.../.../.../.../.../.../test-file.txt",
"File Serving dev mode should prevent traversing with /.../.../.../.../.../.../test-file.txt",
"File Serving dev mode should prevent traversing with /.../.../.../.../.../test-file.txt",
"File Serving dev mode should prevent traversing with /.../.../.../.../test-file.txt",
"File Serving dev mode should prevent traversing with /.../.../.../test-file.txt",
"File Serving dev mode should prevent traversing with /.../.../test-file.txt",
"File Serving dev mode should prevent traversing with /.../test-file.txt",
"File Serving dev mode should prevent traversing with /...\\...\\...\\...\\...\\...\\...\\...\\test-file.txt",
"File Serving dev mode should prevent traversing with /...\\...\\...\\...\\...\\...\\...\\test-file.txt",
"File Serving dev mode should prevent traversing with /...\\...\\...\\...\\...\\...\\test-file.txt",
"File Serving dev mode should prevent traversing with /...\\...\\...\\...\\...\\test-file.txt",
"File Serving dev mode should prevent traversing with /...\\...\\...\\...\\test-file.txt",
"File Serving dev mode should prevent traversing with /...\\...\\...\\test-file.txt",
"File Serving dev mode should prevent traversing with /...\\...\\test-file.txt",
"File Serving dev mode should prevent traversing with /...\\test-file.txt",
"File Serving dev mode should prevent traversing with /../../../../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /../../../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /../../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /../../../test-file.txt",
"File Serving dev mode should prevent traversing with /../..//../..//../..//../..///test-file.txt",
"File Serving dev mode should prevent traversing with /../..//../..//../..//../..//test-file.txt",
"File Serving dev mode should prevent traversing with /../..//../..//../..//..///test-file.txt",
"File Serving dev mode should prevent traversing with /../..//../..//../..//../test-file.txt",
"File Serving dev mode should prevent traversing with /../..//../..//../..///test-file.txt",
"File Serving dev mode should prevent traversing with /../..//../..//../..//test-file.txt",
"File Serving dev mode should prevent traversing with /../..//../..//..///test-file.txt",
"File Serving dev mode should prevent traversing with /../..//../..//../test-file.txt",
"File Serving dev mode should prevent traversing with /../..//../..///test-file.txt",
"File Serving dev mode should prevent traversing with /../..//../..//test-file.txt",
"File Serving dev mode should prevent traversing with /../..//..///test-file.txt",
"File Serving dev mode should prevent traversing with /../..//../test-file.txt",
"File Serving dev mode should prevent traversing with /../..///test-file.txt",
"File Serving dev mode should prevent traversing with /../..//test-file.txt",
"File Serving dev mode should prevent traversing with /../../test-file.txt",
"File Serving dev mode should prevent traversing with /..//..//..//..//..//..//..//..//test-file.txt",
"File Serving dev mode should prevent traversing with /..//..//..//..//..//..//..//test-file.txt",
"File Serving dev mode should prevent traversing with /..//..//..//..//..//..//test-file.txt",
"File Serving dev mode should prevent traversing with /..//..//..//..//..//test-file.txt",
"File Serving dev mode should prevent traversing with /..//..//..//..//test-file.txt",
"File Serving dev mode should prevent traversing with /..//..//..//test-file.txt",
"File Serving dev mode should prevent traversing with /..//..//test-file.txt",
"File Serving dev mode should prevent traversing with /..///..///..///..///..///..///..///..///test-file.txt",
"File Serving dev mode should prevent traversing with /..///..///..///..///..///..///..///test-file.txt",
"File Serving dev mode should prevent traversing with /..///..///..///..///..///..///test-file.txt",
"File Serving dev mode should prevent traversing with /..///..///..///..///..///test-file.txt",
"File Serving dev mode should prevent traversing with /..///..///..///..///test-file.txt",
"File Serving dev mode should prevent traversing with /..///..///..///test-file.txt",
"File Serving dev mode should prevent traversing with /..///..///test-file.txt",
"File Serving dev mode should prevent traversing with /..///test-file.txt",
"File Serving dev mode should prevent traversing with /..//test-file.txt",
"File Serving dev mode should prevent traversing with /../test-file.txt",
"File Serving dev mode should prevent traversing with /..0x2f..0x2f..0x2f..0x2f..0x2f..0x2f..0x2f..0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..0x2f..0x2f..0x2f..0x2f..0x2f..0x2f..0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..0x2f..0x2f..0x2f..0x2f..0x2f..0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..0x2f..0x2f..0x2f..0x2f..0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..0x2f..0x2f..0x2f..0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..0x2f..0x2f..0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..0x2f..0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /..0x5c..0x5c..0x5c..0x5c..0x5c..0x5c..0x5c..0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..0x5c..0x5c..0x5c..0x5c..0x5c..0x5c..0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..0x5c..0x5c..0x5c..0x5c..0x5c..0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..0x5c..0x5c..0x5c..0x5c..0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..0x5c..0x5c..0x5c..0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..0x5c..0x5c..0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..0x5c..0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\..\\\\..\\..\\\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\..\\\\..\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\..\\\\..\\\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\..\\\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\..\\\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\\\..\\..\\\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\\\..\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\\\..\\\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\..\\\\..\\\\..\\\\..\\\\..\\\\..\\\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\..\\\\..\\\\..\\\\..\\\\..\\\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\..\\\\..\\\\..\\\\..\\\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\..\\\\..\\\\..\\\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\..\\\\..\\\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\..\\\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\\\..\\\\\\..\\\\\\..\\\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\\\..\\\\\\..\\\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\\\..\\\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /..\\test-file.txt",
"File Serving dev mode should prevent traversing with /./.././.././.././.././.././.././.././../test-file.txt",
"File Serving dev mode should prevent traversing with /./.././.././.././.././.././.././../test-file.txt",
"File Serving dev mode should prevent traversing with /./.././.././.././.././.././../test-file.txt",
"File Serving dev mode should prevent traversing with /./.././.././.././.././../test-file.txt",
"File Serving dev mode should prevent traversing with /./.././.././.././../test-file.txt",
"File Serving dev mode should prevent traversing with /./.././.././../test-file.txt",
"File Serving dev mode should prevent traversing with /./.././../test-file.txt",
"File Serving dev mode should prevent traversing with /./../test-file.txt",
"File Serving dev mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../../../../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../../../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../../../test-file.txt",
"File Serving dev mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../../test-file.txt",
"File Serving dev mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../test-file.txt",
"File Serving dev mode should prevent traversing with /.//..//.//..//.//..//.//..//.//..//.//..//.//..//.//..//test-file.txt",
"File Serving dev mode should prevent traversing with /.//..//.//..//.//..//.//..//.//..//.//..//.//..//test-file.txt",
"File Serving dev mode should prevent traversing with /.//..//.//..//.//..//.//..//.//..//.//..//test-file.txt",
"File Serving dev mode should prevent traversing with /.//..//.//..//.//..//.//..//.//..//test-file.txt",
"File Serving dev mode should prevent traversing with /.//..//.//..//.//..//.//..//test-file.txt",
"File Serving dev mode should prevent traversing with /.//..//.//..//.//..//test-file.txt",
"File Serving dev mode should prevent traversing with /.//..//.//..//test-file.txt",
"File Serving dev mode should prevent traversing with /.//..//test-file.txt",
"File Serving dev mode should prevent traversing with /./\\/././\\/././\\/././\\/././\\/././\\/././\\/././\\/./test-file.txt",
"File Serving dev mode should prevent traversing with /./\\/././\\/././\\/././\\/././\\/././\\/././\\/./test-file.txt",
"File Serving dev mode should prevent traversing with /./\\/././\\/././\\/././\\/././\\/././\\/./test-file.txt",
"File Serving dev mode should prevent traversing with /./\\/././\\/././\\/././\\/././\\/./test-file.txt",
"File Serving dev mode should prevent traversing with /./\\/././\\/././\\/././\\/./test-file.txt",
"File Serving dev mode should prevent traversing with /./\\/././\\/././\\/./test-file.txt",
"File Serving dev mode should prevent traversing with /./\\/././\\/./test-file.txt",
"File Serving dev mode should prevent traversing with /./\\/./test-file.txt",
"File Serving dev mode should prevent traversing with /.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\..\\.\\..\\.\\..\\.\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\..\\.\\..\\.\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\..\\.\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\/\\.\\.\\/\\.\\.\\/\\.\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\/\\.\\.\\/\\.\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\/\\.\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\\\..\\\\.\\\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with /.\\\\..\\\\test-file.txt",
"File Serving dev mode should prevent traversing with //..\\/..\\/..\\/..\\/..\\/..\\/..\\/..\\test-file.txt",
"File Serving dev mode should prevent traversing with //..\\/..\\/..\\/..\\/..\\/..\\/..\\test-file.txt",
"File Serving dev mode should prevent traversing with //..\\/..\\/..\\/..\\/..\\/..\\test-file.txt",
"File Serving dev mode should prevent traversing with //..\\/..\\/..\\/..\\/..\\test-file.txt",
"File Serving dev mode should prevent traversing with //..\\/..\\/..\\/..\\test-file.txt",
"File Serving dev mode should prevent traversing with //..\\/..\\/..\\test-file.txt",
"File Serving dev mode should prevent traversing with //..\\/..\\test-file.txt",
"File Serving dev mode should prevent traversing with //..\\test-file.txt",
"File Serving dev mode should prevent traversing with ////%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with ////%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with ////%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with ////%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with ////%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with ////%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with ////%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with ////%2e%2e%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/test-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/test-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/test-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/test-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/test-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e/0x2e0x2e/0x2e0x2e/test-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e/0x2e0x2e/test-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e/test-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x2f0x2e0x2e0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x2ftest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x5c0x2e0x2e0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e0x5ctest-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e\\0x2e0x2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /0x2e0x2e\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\test-file.txt",
"File Serving dev mode should prevent traversing with /\\..%2f",
"File Serving dev mode should prevent traversing with /\\..%2f\\..%2f",
"File Serving dev mode should prevent traversing with /\\..%2f\\..%2f\\..%2f",
"File Serving dev mode should prevent traversing with /\\..%2f\\..%2f\\..%2f\\..%2f",
"File Serving dev mode should prevent traversing with /\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f",
"File Serving dev mode should prevent traversing with /\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f",
"File Serving dev mode should prevent traversing with /\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f",
"File Serving dev mode should prevent traversing with /\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f\\..%2ftest-file.txt",
"File Serving dev mode should prevent traversing with /\\../\\../\\../\\../\\../\\../\\../\\../test-file.txt",
"File Serving dev mode should prevent traversing with /\\../\\../\\../\\../\\../\\../\\../test-file.txt",
"File Serving dev mode should prevent traversing with /\\../\\../\\../\\../\\../\\../test-file.txt",
"File Serving dev mode should prevent traversing with /\\../\\../\\../\\../\\../test-file.txt",
"File Serving dev mode should prevent traversing with /\\../\\../\\../\\../test-file.txt",
"File Serving dev mode should prevent traversing with /\\../\\../\\../test-file.txt",
"File Serving dev mode should prevent traversing with /\\../\\../test-file.txt",
"File Serving dev mode should prevent traversing with /\\../test-file.txt",
"File Serving dev mode should prevent traversing with /\\\\\\%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /\\\\\\%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /\\\\\\%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /\\\\\\%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /\\\\\\%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /\\\\\\%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /\\\\\\%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving dev mode should prevent traversing with /\\\\\\%2e%2e%5ctest-file.txt",
"File Serving dev mode should serve avif image with correct content-type",
"File Serving dev mode should serve correct error code",
"File Serving dev mode should serve file with space correctly from public/",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"File Serving dev mode should serve file with space correctly static/"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%32%66%%32%65%%32%65%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%35%63%%32%65%%32%65%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65/%%32%65%%32%65/%%32%65%%32%65/test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65/%%32%65%%32%65/test-file.txt",
"File Serving production mode should prevent traversing with /%%32%65%%32%65/test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252ftest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252ftest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252ftest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252ftest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%252f%252e%252e%252f%252e%252e%252f%252e%252e%252ftest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%252f%252e%252e%252f%252e%252e%252ftest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%252f%252e%252e%252ftest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%252ftest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255ctest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255ctest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255ctest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255ctest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%255c%252e%252e%255c%252e%252e%255c%252e%252e%255ctest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%255c%252e%252e%255c%252e%252e%255ctest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%255c%252e%252e%255ctest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e%255ctest-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e/%252e%252e/%252e%252e/%252e%252e/%252e%252e/test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e/%252e%252e/%252e%252e/%252e%252e/test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e/%252e%252e/%252e%252e/test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e/%252e%252e/test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e/test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e\\%252e%252e\\%252e%252e\\%252e%252e\\test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e\\%252e%252e\\%252e%252e\\test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e\\%252e%252e\\test-file.txt",
"File Serving production mode should prevent traversing with /%252e%252e\\test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25af%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259c%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae/%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae/test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae\\%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%25c0%25ae%25c0%25ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e/%2e%2e/%2e%2e/%2e%2e/%2e%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e/%2e%2e/%2e%2e/%2e%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e/%2e%2e/%2e%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e/%2e%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e\\%2e%2e\\%2e%2e\\%2e%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e\\%2e%2e\\%2e%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e\\%2e%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%2e%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%2f%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%5c%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e/%c0%2e%c0%2e/%c0%2e%c0%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e/%c0%2e%c0%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e\\%c0%2e%c0%2e\\%c0%2e%c0%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e\\%c0%2e%c0%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%2e%c0%2e\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c0%af%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c1%9c%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae/%c0%ae%c0%ae/%c0%ae%c0%ae/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae/%c0%ae%c0%ae/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae/test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae\\%c0%ae%c0%ae\\%c0%ae%c0%ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae\\%c0%ae%c0%ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%c0%ae%c0%ae\\test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2215%uff0e%uff0e%u2215%uff0e%uff0e%u2215test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2215%uff0e%uff0e%u2215test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2215test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2216%uff0e%uff0e%u2216%uff0e%uff0e%u2216test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2216%uff0e%uff0e%u2216test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e%u2216test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e/%uff0e%uff0e/%uff0e%uff0e/test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e/%uff0e%uff0e/test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e/test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e\\%uff0e%uff0e\\%uff0e%uff0e\\test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e\\%uff0e%uff0e\\test-file.txt",
"File Serving production mode should prevent traversing with /%uff0e%uff0e\\test-file.txt",
"File Serving production mode should prevent traversing with /..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /..%%32%66..%%32%66..%%32%66..%%32%66..%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /..%%32%66..%%32%66..%%32%66..%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /..%%32%66..%%32%66..%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /..%%32%66..%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /..%%32%66test-file.txt",
"File Serving production mode should prevent traversing with /..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /..%%35%63..%%35%63..%%35%63..%%35%63..%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /..%%35%63..%%35%63..%%35%63..%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /..%%35%63..%%35%63..%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /..%%35%63..%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /..%%35%63test-file.txt",
"File Serving production mode should prevent traversing with /..%252f..%252f..%252f..%252f..%252f..%252f..%252f..%252ftest-file.txt",
"File Serving production mode should prevent traversing with /..%252f..%252f..%252f..%252f..%252f..%252f..%252ftest-file.txt",
"File Serving production mode should prevent traversing with /..%252f..%252f..%252f..%252f..%252f..%252ftest-file.txt",
"File Serving production mode should prevent traversing with /..%252f..%252f..%252f..%252f..%252ftest-file.txt",
"File Serving production mode should prevent traversing with /..%252f..%252f..%252f..%252ftest-file.txt",
"File Serving production mode should prevent traversing with /..%252f..%252f..%252ftest-file.txt",
"File Serving production mode should prevent traversing with /..%252f..%252ftest-file.txt",
"File Serving production mode should prevent traversing with /..%252ftest-file.txt",
"File Serving production mode should prevent traversing with /..%255c..%255c..%255c..%255c..%255c..%255c..%255c..%255ctest-file.txt",
"File Serving production mode should prevent traversing with /..%255c..%255c..%255c..%255c..%255c..%255c..%255ctest-file.txt",
"File Serving production mode should prevent traversing with /..%255c..%255c..%255c..%255c..%255c..%255ctest-file.txt",
"File Serving production mode should prevent traversing with /..%255c..%255c..%255c..%255c..%255ctest-file.txt",
"File Serving production mode should prevent traversing with /..%255c..%255c..%255c..%255ctest-file.txt",
"File Serving production mode should prevent traversing with /..%255c..%255c..%255ctest-file.txt",
"File Serving production mode should prevent traversing with /..%255c..%255ctest-file.txt",
"File Serving production mode should prevent traversing with /..%255ctest-file.txt",
"File Serving production mode should prevent traversing with /..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /..%25c0%25af..%25c0%25af..%25c0%25af..%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /..%25c0%25af..%25c0%25af..%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /..%25c0%25af..%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /..%25c0%25aftest-file.txt",
"File Serving production mode should prevent traversing with /..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /..%25c1%259c..%25c1%259c..%25c1%259c..%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /..%25c1%259c..%25c1%259c..%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /..%25c1%259c..%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /..%25c1%259ctest-file.txt",
"File Serving production mode should prevent traversing with /..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%2f..%2f..%2f..%2f..%2f..%2f..%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%2f..%2f..%2f..%2f..%2f..%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%2f..%2f..%2f..%2f..%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%2f..%2f..%2f..%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%2f..%2f..%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%2f..%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%5c..%5c..%5c..%5c..%5c..%5c..%5c..%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%5c..%5c..%5c..%5c..%5c..%5c..%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%5c..%5c..%5c..%5c..%5c..%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%5c..%5c..%5c..%5c..%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%5c..%5c..%5c..%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%5c..%5c..%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%5c..%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%2f..%c0%2f..%c0%2f..%c0%2f..%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%2f..%c0%2f..%c0%2f..%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%2f..%c0%2f..%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%2f..%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%2ftest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%5c..%c0%5c..%c0%5c..%c0%5c..%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%5c..%c0%5c..%c0%5c..%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%5c..%c0%5c..%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%5c..%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%5ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%af..%c0%af..%c0%af..%c0%af..%c0%af..%c0%af..%c0%af..%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%af..%c0%af..%c0%af..%c0%af..%c0%af..%c0%af..%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%af..%c0%af..%c0%af..%c0%af..%c0%af..%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%af..%c0%af..%c0%af..%c0%af..%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%af..%c0%af..%c0%af..%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%af..%c0%af..%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%af..%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /..%c0%aftest-file.txt",
"File Serving production mode should prevent traversing with /..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c1%9c..%c1%9c..%c1%9c..%c1%9c..%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c1%9c..%c1%9c..%c1%9c..%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c1%9c..%c1%9c..%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c1%9c..%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /..%c1%9ctest-file.txt",
"File Serving production mode should prevent traversing with /..%u2215..%u2215..%u2215..%u2215..%u2215..%u2215..%u2215..%u2215test-file.txt",
"File Serving production mode should prevent traversing with /..%u2215..%u2215..%u2215..%u2215..%u2215..%u2215..%u2215test-file.txt",
"File Serving production mode should prevent traversing with /..%u2215..%u2215..%u2215..%u2215..%u2215..%u2215test-file.txt",
"File Serving production mode should prevent traversing with /..%u2215..%u2215..%u2215..%u2215..%u2215test-file.txt",
"File Serving production mode should prevent traversing with /..%u2215..%u2215..%u2215..%u2215test-file.txt",
"File Serving production mode should prevent traversing with /..%u2215..%u2215..%u2215test-file.txt",
"File Serving production mode should prevent traversing with /..%u2215..%u2215test-file.txt",
"File Serving production mode should prevent traversing with /..%u2215test-file.txt",
"File Serving production mode should prevent traversing with /..%u2216..%u2216..%u2216..%u2216..%u2216..%u2216..%u2216..%u2216test-file.txt",
"File Serving production mode should prevent traversing with /..%u2216..%u2216..%u2216..%u2216..%u2216..%u2216..%u2216test-file.txt",
"File Serving production mode should prevent traversing with /..%u2216..%u2216..%u2216..%u2216..%u2216..%u2216test-file.txt",
"File Serving production mode should prevent traversing with /..%u2216..%u2216..%u2216..%u2216..%u2216test-file.txt",
"File Serving production mode should prevent traversing with /..%u2216..%u2216..%u2216..%u2216test-file.txt",
"File Serving production mode should prevent traversing with /..%u2216..%u2216..%u2216test-file.txt",
"File Serving production mode should prevent traversing with /..%u2216..%u2216test-file.txt",
"File Serving production mode should prevent traversing with /..%u2216test-file.txt",
"File Serving production mode should prevent traversing with /..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8test-file.txt",
"File Serving production mode should prevent traversing with /..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8test-file.txt",
"File Serving production mode should prevent traversing with /..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8test-file.txt",
"File Serving production mode should prevent traversing with /..%uEFC8..%uEFC8..%uEFC8..%uEFC8..%uEFC8test-file.txt",
"File Serving production mode should prevent traversing with /..%uEFC8..%uEFC8..%uEFC8..%uEFC8test-file.txt",
"File Serving production mode should prevent traversing with /..%uEFC8..%uEFC8..%uEFC8test-file.txt",
"File Serving production mode should prevent traversing with /..%uEFC8..%uEFC8test-file.txt",
"File Serving production mode should prevent traversing with /..%uEFC8test-file.txt",
"File Serving production mode should prevent traversing with /..%uF025..%uF025..%uF025..%uF025..%uF025..%uF025..%uF025..%uF025test-file.txt",
"File Serving production mode should prevent traversing with /..%uF025..%uF025..%uF025..%uF025..%uF025..%uF025..%uF025test-file.txt",
"File Serving production mode should prevent traversing with /..%uF025..%uF025..%uF025..%uF025..%uF025..%uF025test-file.txt",
"File Serving production mode should prevent traversing with /..%uF025..%uF025..%uF025..%uF025..%uF025test-file.txt",
"File Serving production mode should prevent traversing with /..%uF025..%uF025..%uF025..%uF025test-file.txt",
"File Serving production mode should prevent traversing with /..%uF025..%uF025..%uF025test-file.txt",
"File Serving production mode should prevent traversing with /..%uF025..%uF025test-file.txt",
"File Serving production mode should prevent traversing with /..%uF025test-file.txt",
"File Serving production mode should prevent traversing with /........................................................................../../../../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /........................................................................../../../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /........................................................................../../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /........................................................................../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /........................................................................../../../../test-file.txt",
"File Serving production mode should prevent traversing with /........................................................................../../../test-file.txt",
"File Serving production mode should prevent traversing with /........................................................................../../test-file.txt",
"File Serving production mode should prevent traversing with /........................................................................../test-file.txt",
"File Serving production mode should prevent traversing with /..........................................................................\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..........................................................................\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..........................................................................\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..........................................................................\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..........................................................................\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..........................................................................\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..........................................................................\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..........................................................................\\test-file.txt",
"File Serving production mode should prevent traversing with /..../..../..../..../..../..../..../..../test-file.txt",
"File Serving production mode should prevent traversing with /..../..../..../..../..../..../..../test-file.txt",
"File Serving production mode should prevent traversing with /..../..../..../..../..../..../test-file.txt",
"File Serving production mode should prevent traversing with /..../..../..../..../..../test-file.txt",
"File Serving production mode should prevent traversing with /..../..../..../..../test-file.txt",
"File Serving production mode should prevent traversing with /..../..../..../test-file.txt",
"File Serving production mode should prevent traversing with /..../..../test-file.txt",
"File Serving production mode should prevent traversing with /..../test-file.txt",
"File Serving production mode should prevent traversing with /....\\....\\....\\....\\....\\....\\....\\....\\test-file.txt",
"File Serving production mode should prevent traversing with /....\\....\\....\\....\\....\\....\\....\\test-file.txt",
"File Serving production mode should prevent traversing with /....\\....\\....\\....\\....\\....\\test-file.txt",
"File Serving production mode should prevent traversing with /....\\....\\....\\....\\....\\test-file.txt",
"File Serving production mode should prevent traversing with /....\\....\\....\\....\\test-file.txt",
"File Serving production mode should prevent traversing with /....\\....\\....\\test-file.txt",
"File Serving production mode should prevent traversing with /....\\....\\test-file.txt",
"File Serving production mode should prevent traversing with /....\\test-file.txt",
"File Serving production mode should prevent traversing with /.../.../.../.../.../.../.../.../test-file.txt",
"File Serving production mode should prevent traversing with /.../.../.../.../.../.../.../test-file.txt",
"File Serving production mode should prevent traversing with /.../.../.../.../.../.../test-file.txt",
"File Serving production mode should prevent traversing with /.../.../.../.../.../test-file.txt",
"File Serving production mode should prevent traversing with /.../.../.../.../test-file.txt",
"File Serving production mode should prevent traversing with /.../.../.../test-file.txt",
"File Serving production mode should prevent traversing with /.../.../test-file.txt",
"File Serving production mode should prevent traversing with /.../test-file.txt",
"File Serving production mode should prevent traversing with /...\\...\\...\\...\\...\\...\\...\\...\\test-file.txt",
"File Serving production mode should prevent traversing with /...\\...\\...\\...\\...\\...\\...\\test-file.txt",
"File Serving production mode should prevent traversing with /...\\...\\...\\...\\...\\...\\test-file.txt",
"File Serving production mode should prevent traversing with /...\\...\\...\\...\\...\\test-file.txt",
"File Serving production mode should prevent traversing with /...\\...\\...\\...\\test-file.txt",
"File Serving production mode should prevent traversing with /...\\...\\...\\test-file.txt",
"File Serving production mode should prevent traversing with /...\\...\\test-file.txt",
"File Serving production mode should prevent traversing with /...\\test-file.txt",
"File Serving production mode should prevent traversing with /../../../../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /../../../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /../../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /../../../../test-file.txt",
"File Serving production mode should prevent traversing with /../../../test-file.txt",
"File Serving production mode should prevent traversing with /../..//../..//../..//../..///test-file.txt",
"File Serving production mode should prevent traversing with /../..//../..//../..//../..//test-file.txt",
"File Serving production mode should prevent traversing with /../..//../..//../..//..///test-file.txt",
"File Serving production mode should prevent traversing with /../..//../..//../..//../test-file.txt",
"File Serving production mode should prevent traversing with /../..//../..//../..///test-file.txt",
"File Serving production mode should prevent traversing with /../..//../..//../..//test-file.txt",
"File Serving production mode should prevent traversing with /../..//../..//..///test-file.txt",
"File Serving production mode should prevent traversing with /../..//../..//../test-file.txt",
"File Serving production mode should prevent traversing with /../..//../..///test-file.txt",
"File Serving production mode should prevent traversing with /../..//../..//test-file.txt",
"File Serving production mode should prevent traversing with /../..//..///test-file.txt",
"File Serving production mode should prevent traversing with /../..//../test-file.txt",
"File Serving production mode should prevent traversing with /../..///test-file.txt",
"File Serving production mode should prevent traversing with /../..//test-file.txt",
"File Serving production mode should prevent traversing with /../../test-file.txt",
"File Serving production mode should prevent traversing with /..//..//..//..//..//..//..//..//test-file.txt",
"File Serving production mode should prevent traversing with /..//..//..//..//..//..//..//test-file.txt",
"File Serving production mode should prevent traversing with /..//..//..//..//..//..//test-file.txt",
"File Serving production mode should prevent traversing with /..//..//..//..//..//test-file.txt",
"File Serving production mode should prevent traversing with /..//..//..//..//test-file.txt",
"File Serving production mode should prevent traversing with /..//..//..//test-file.txt",
"File Serving production mode should prevent traversing with /..//..//test-file.txt",
"File Serving production mode should prevent traversing with /..///..///..///..///..///..///..///..///test-file.txt",
"File Serving production mode should prevent traversing with /..///..///..///..///..///..///..///test-file.txt",
"File Serving production mode should prevent traversing with /..///..///..///..///..///..///test-file.txt",
"File Serving production mode should prevent traversing with /..///..///..///..///..///test-file.txt",
"File Serving production mode should prevent traversing with /..///..///..///..///test-file.txt",
"File Serving production mode should prevent traversing with /..///..///..///test-file.txt",
"File Serving production mode should prevent traversing with /..///..///test-file.txt",
"File Serving production mode should prevent traversing with /..///test-file.txt",
"File Serving production mode should prevent traversing with /..//test-file.txt",
"File Serving production mode should prevent traversing with /../test-file.txt",
"File Serving production mode should prevent traversing with /..0x2f..0x2f..0x2f..0x2f..0x2f..0x2f..0x2f..0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /..0x2f..0x2f..0x2f..0x2f..0x2f..0x2f..0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /..0x2f..0x2f..0x2f..0x2f..0x2f..0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /..0x2f..0x2f..0x2f..0x2f..0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /..0x2f..0x2f..0x2f..0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /..0x2f..0x2f..0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /..0x2f..0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /..0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /..0x5c..0x5c..0x5c..0x5c..0x5c..0x5c..0x5c..0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /..0x5c..0x5c..0x5c..0x5c..0x5c..0x5c..0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /..0x5c..0x5c..0x5c..0x5c..0x5c..0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /..0x5c..0x5c..0x5c..0x5c..0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /..0x5c..0x5c..0x5c..0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /..0x5c..0x5c..0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /..0x5c..0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /..0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\..\\\\..\\..\\\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\..\\\\..\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\..\\\\..\\\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\..\\\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\..\\\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\\\..\\..\\\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\\\..\\..\\\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\\\..\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\\\..\\\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\..\\\\..\\\\..\\\\..\\\\..\\\\..\\\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\..\\\\..\\\\..\\\\..\\\\..\\\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\..\\\\..\\\\..\\\\..\\\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\..\\\\..\\\\..\\\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\..\\\\..\\\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\..\\\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\\\..\\\\\\..\\\\\\..\\\\\\..\\\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\\\..\\\\\\..\\\\\\..\\\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\\\..\\\\\\..\\\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\\\..\\\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /..\\test-file.txt",
"File Serving production mode should prevent traversing with /./.././.././.././.././.././.././.././../test-file.txt",
"File Serving production mode should prevent traversing with /./.././.././.././.././.././.././../test-file.txt",
"File Serving production mode should prevent traversing with /./.././.././.././.././.././../test-file.txt",
"File Serving production mode should prevent traversing with /./.././.././.././.././../test-file.txt",
"File Serving production mode should prevent traversing with /./.././.././.././../test-file.txt",
"File Serving production mode should prevent traversing with /./.././.././../test-file.txt",
"File Serving production mode should prevent traversing with /./.././../test-file.txt",
"File Serving production mode should prevent traversing with /./../test-file.txt",
"File Serving production mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../../../../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../../../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../../../../test-file.txt",
"File Serving production mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../../../test-file.txt",
"File Serving production mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../../test-file.txt",
"File Serving production mode should prevent traversing with /././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././././../test-file.txt",
"File Serving production mode should prevent traversing with /.//..//.//..//.//..//.//..//.//..//.//..//.//..//.//..//test-file.txt",
"File Serving production mode should prevent traversing with /.//..//.//..//.//..//.//..//.//..//.//..//.//..//test-file.txt",
"File Serving production mode should prevent traversing with /.//..//.//..//.//..//.//..//.//..//.//..//test-file.txt",
"File Serving production mode should prevent traversing with /.//..//.//..//.//..//.//..//.//..//test-file.txt",
"File Serving production mode should prevent traversing with /.//..//.//..//.//..//.//..//test-file.txt",
"File Serving production mode should prevent traversing with /.//..//.//..//.//..//test-file.txt",
"File Serving production mode should prevent traversing with /.//..//.//..//test-file.txt",
"File Serving production mode should prevent traversing with /.//..//test-file.txt",
"File Serving production mode should prevent traversing with /./\\/././\\/././\\/././\\/././\\/././\\/././\\/././\\/./test-file.txt",
"File Serving production mode should prevent traversing with /./\\/././\\/././\\/././\\/././\\/././\\/././\\/./test-file.txt",
"File Serving production mode should prevent traversing with /./\\/././\\/././\\/././\\/././\\/././\\/./test-file.txt",
"File Serving production mode should prevent traversing with /./\\/././\\/././\\/././\\/././\\/./test-file.txt",
"File Serving production mode should prevent traversing with /./\\/././\\/././\\/././\\/./test-file.txt",
"File Serving production mode should prevent traversing with /./\\/././\\/././\\/./test-file.txt",
"File Serving production mode should prevent traversing with /./\\/././\\/./test-file.txt",
"File Serving production mode should prevent traversing with /./\\/./test-file.txt",
"File Serving production mode should prevent traversing with /.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\..\\.\\..\\.\\..\\.\\..\\.\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\..\\.\\..\\.\\..\\.\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\..\\.\\..\\.\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\..\\.\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\/\\.\\.\\/\\.\\.\\/\\.\\.\\/\\.\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\/\\.\\.\\/\\.\\.\\/\\.\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\/\\.\\.\\/\\.\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\/\\.\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\\\..\\\\.\\\\..\\\\.\\\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\\\..\\\\.\\\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with /.\\\\..\\\\test-file.txt",
"File Serving production mode should prevent traversing with //..\\/..\\/..\\/..\\/..\\/..\\/..\\/..\\test-file.txt",
"File Serving production mode should prevent traversing with //..\\/..\\/..\\/..\\/..\\/..\\/..\\test-file.txt",
"File Serving production mode should prevent traversing with //..\\/..\\/..\\/..\\/..\\/..\\test-file.txt",
"File Serving production mode should prevent traversing with //..\\/..\\/..\\/..\\/..\\test-file.txt",
"File Serving production mode should prevent traversing with //..\\/..\\/..\\/..\\test-file.txt",
"File Serving production mode should prevent traversing with //..\\/..\\/..\\test-file.txt",
"File Serving production mode should prevent traversing with //..\\/..\\test-file.txt",
"File Serving production mode should prevent traversing with //..\\test-file.txt",
"File Serving production mode should prevent traversing with ////%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with ////%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with ////%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with ////%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with ////%2e%2e%2f%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with ////%2e%2e%2f%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with ////%2e%2e%2f%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with ////%2e%2e%2ftest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/test-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/test-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/test-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/test-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e/0x2e0x2e/0x2e0x2e/0x2e0x2e/test-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e/0x2e0x2e/0x2e0x2e/test-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e/0x2e0x2e/test-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e/test-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x2f0x2e0x2e0x2f0x2e0x2e0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x2f0x2e0x2e0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x2ftest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x5c0x2e0x2e0x5c0x2e0x2e0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x5c0x2e0x2e0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e0x5ctest-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\test-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\test-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\test-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\test-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\test-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e\\0x2e0x2e\\0x2e0x2e\\test-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e\\0x2e0x2e\\test-file.txt",
"File Serving production mode should prevent traversing with /0x2e0x2e\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/../test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\\..\\test-file.txt",
"File Serving production mode should prevent traversing with /\\..%2f",
"File Serving production mode should prevent traversing with /\\..%2f\\..%2f",
"File Serving production mode should prevent traversing with /\\..%2f\\..%2f\\..%2f",
"File Serving production mode should prevent traversing with /\\..%2f\\..%2f\\..%2f\\..%2f",
"File Serving production mode should prevent traversing with /\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f",
"File Serving production mode should prevent traversing with /\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f",
"File Serving production mode should prevent traversing with /\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f",
"File Serving production mode should prevent traversing with /\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f\\..%2f\\..%2ftest-file.txt",
"File Serving production mode should prevent traversing with /\\../\\../\\../\\../\\../\\../\\../\\../test-file.txt",
"File Serving production mode should prevent traversing with /\\../\\../\\../\\../\\../\\../\\../test-file.txt",
"File Serving production mode should prevent traversing with /\\../\\../\\../\\../\\../\\../test-file.txt",
"File Serving production mode should prevent traversing with /\\../\\../\\../\\../\\../test-file.txt",
"File Serving production mode should prevent traversing with /\\../\\../\\../\\../test-file.txt",
"File Serving production mode should prevent traversing with /\\../\\../\\../test-file.txt",
"File Serving production mode should prevent traversing with /\\../\\../test-file.txt",
"File Serving production mode should prevent traversing with /\\../test-file.txt",
"File Serving production mode should prevent traversing with /\\\\\\%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving production mode should prevent traversing with /\\\\\\%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving production mode should prevent traversing with /\\\\\\%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving production mode should prevent traversing with /\\\\\\%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving production mode should prevent traversing with /\\\\\\%2e%2e%5c%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving production mode should prevent traversing with /\\\\\\%2e%2e%5c%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving production mode should prevent traversing with /\\\\\\%2e%2e%5c%2e%2e%5ctest-file.txt",
"File Serving production mode should prevent traversing with /\\\\\\%2e%2e%5ctest-file.txt",
"File Serving production mode should serve avif image with correct content-type",
"File Serving production mode should serve correct error code",
"File Serving production mode should serve file with space correctly from public/",
"File Serving production mode should serve file with space correctly static/"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/filesystempublicroutes/test/index.test.js": {
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"passed": [
"FileSystemPublicRoutes should route to public folder files",
"FileSystemPublicRoutes should still handle /_next routes"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"FileSystemPublicRoutes should not route to the index page",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"FileSystemPublicRoutes should route to exportPathMap defined routes in development"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/firebase-grpc/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Building Firebase production mode Throws an error when building with firebase dependency with worker_threads",
"Building Firebase production mode Throws no error when building with firebase dependency without worker_threads"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/font-optimization/test/index.test.js": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Font Optimization Spread operator regression on <link>",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Font Optimization font override production mode should inline font-override values",
"Font Optimization font override with size adjust production mode should inline font-override values",
"Font Optimization invalid configuration production mode should show a proper error if assetPrefix starts with .",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Font Optimization makeStylesheetInert regression",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Font Optimization with-google Font optimization for SSR apps production mode should add preconnect tag",
"Font Optimization with-google Font optimization for SSR apps production mode should inline the google fonts for SSR pages",
"Font Optimization with-google Font optimization for SSR apps production mode should inline the google fonts for static pages",
"Font Optimization with-google Font optimization for SSR apps production mode should inline the google fonts for static pages with Next/Head",
"Font Optimization with-google Font optimization for SSR apps production mode should only inline included fonts per page",
"Font Optimization with-google Font optimization for SSR apps production mode should pass nonce to the inlined font definition",
"Font Optimization with-google Font optimization for SSR apps production mode should skip this optimization for AMP pages",
"Font Optimization with-google Font optimization for SSR apps production mode should work for fonts loaded on navigation",
"Font Optimization with-google Font optimization for SSR apps production mode should work when build is cached",
"Font Optimization with-google Font optimization for unreachable font definitions. production mode should fallback to normal stylesheet if the contents of the fonts are unreachable",
"Font Optimization with-google Font optimization for unreachable font definitions. production mode should not inline multiple fallback link tag",
"Font Optimization with-typekit Font optimization for SSR apps production mode should add preconnect tag",
"Font Optimization with-typekit Font optimization for SSR apps production mode should inline the typekit fonts for SSR pages",
"Font Optimization with-typekit Font optimization for SSR apps production mode should inline the typekit fonts for static pages",
"Font Optimization with-typekit Font optimization for SSR apps production mode should inline the typekit fonts for static pages with Next/Head",
"Font Optimization with-typekit Font optimization for SSR apps production mode should only inline included fonts per page",
"Font Optimization with-typekit Font optimization for SSR apps production mode should pass nonce to the inlined font definition",
"Font Optimization with-typekit Font optimization for SSR apps production mode should skip this optimization for AMP pages",
"Font Optimization with-typekit Font optimization for SSR apps production mode should work for fonts loaded on navigation",
"Font Optimization with-typekit Font optimization for SSR apps production mode should work when build is cached",
"Font Optimization with-typekit Font optimization for unreachable font definitions. production mode should fallback to normal stylesheet if the contents of the fonts are unreachable",
"Font Optimization with-typekit Font optimization for unreachable font definitions. production mode should not inline multiple fallback link tag"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/future/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"excludeDefaultMomentLocales production mode should load momentjs"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/getinitialprops/test/index.test.js": {
"passed": [
"getInitialProps dev mode should have correct router.asPath for direct visit dynamic page",
"getInitialProps dev mode should have correct router.asPath for direct visit dynamic page rewrite direct",
"getInitialProps dev mode should have gip in __NEXT_DATA__",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"getInitialProps dev mode should not have gip in __NEXT_DATA__ for non-GIP page"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"getInitialProps production mode should have correct router.asPath for direct visit dynamic page",
"getInitialProps production mode should have correct router.asPath for direct visit dynamic page rewrite direct",
"getInitialProps production mode should have gip in __NEXT_DATA__",
"getInitialProps production mode should not have gip in __NEXT_DATA__ for non-GIP page"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/getserversideprops-export-error/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"getServerSideProps production mode should show error for GSSP during export"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/getserversideprops-preview/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"ServerSide Props Preview Mode Development Mode should enable preview mode",
"ServerSide Props Preview Mode Development Mode should fetch prerendered data",
"ServerSide Props Preview Mode Development Mode should fetch preview data on CST",
"ServerSide Props Preview Mode Development Mode should fetch preview data on SSR",
"ServerSide Props Preview Mode Development Mode should return cookies to be expired after dev server reboot",
"ServerSide Props Preview Mode Development Mode should start development application",
"ServerSide Props Preview Mode Development Mode should start the client-side browser"
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
"pending": [
"ServerSide Props Preview Mode production mode should compile successfully",
"ServerSide Props Preview Mode production mode should enable preview mode",
"ServerSide Props Preview Mode production mode should not return fallback page on preview request",
"ServerSide Props Preview Mode production mode should return cookies to be expired on reset request",
"ServerSide Props Preview Mode production mode should return correct caching headers for data preview request",
"ServerSide Props Preview Mode production mode should return page on first request",
"ServerSide Props Preview Mode production mode should return page on second request",
"ServerSide Props Preview Mode production mode should start production application",
"ServerSide Props Preview Mode production mode should throw error when setting too large of preview data"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/gip-identifier/test/index.test.js": {
"passed": [
"gip identifiers dev mode should have gip and appGip in NEXT_DATA for page with getInitialProps and _app with getInitialProps",
"gip identifiers dev mode should have gip in NEXT_DATA for page with getInitialProps",
"gip identifiers dev mode should not have gip or appGip in NEXT_DATA for page without getInitialProps",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"gip identifiers dev mode should only have appGip in NEXT_DATA for page without getInitialProps and _app with getInitialProps"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"gip identifiers production mode should have gip and appGip in NEXT_DATA for page with getInitialProps and _app with getInitialProps",
"gip identifiers production mode should have gip in NEXT_DATA for page with getInitialProps",
"gip identifiers production mode should not have gip or appGip in NEXT_DATA for page without getInitialProps",
"gip identifiers production mode should only have appGip in NEXT_DATA for page without getInitialProps and _app with getInitialProps"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/gsp-build-errors/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"GSP build errors production mode should fail build from ENOENT in getStaticProps",
"GSP build errors production mode should fail build from module not found",
"GSP build errors production mode should fail build from string error in getStaticProps",
"GSP build errors production mode should fail build from undefined error in getStaticProps",
"GSP build errors production mode should fail build on normal error in getStaticProps",
"GSP build errors production mode should handle non-serializable error in getStaticPaths",
"GSP build errors production mode should handle non-serializable error in getStaticProps"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/gsp-extension/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"GS(S)P with file extension production mode should contain extension in name of json files in _next/data",
"GS(S)P with file extension production mode should render properly for routes with extension",
"GS(S)P with file extension production mode should support slug with different extensions"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/gssp-pageProps-merge/test/index.test.js": {
"passed": [
"pageProps GSSP conflict dev mode should merge _app pageProps and getServerSideProps props",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pageProps GSSP conflict dev mode should merge _app pageProps and getStaticProps props"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pageProps GSSP conflict production mode should merge _app pageProps and getServerSideProps props",
"pageProps GSSP conflict production mode should merge _app pageProps and getStaticProps props"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/gssp-redirect-base-path/test/index.test.js": {
"passed": [
"GS(S)P Redirect Support dev mode should apply permanent redirect when visited directly for GSSP page",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"GS(S)P Redirect Support dev mode should apply redirect when GSP page is navigated to client-side (external)",
"GS(S)P Redirect Support dev mode should apply redirect when GSP page is navigated to client-side (internal)",
"GS(S)P Redirect Support dev mode should apply redirect when GSSP page is navigated to client-side (external)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"GS(S)P Redirect Support dev mode should apply redirect when GSSP page is navigated to client-side (internal dynamic)",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"GS(S)P Redirect Support dev mode should apply redirect when GSSP page is navigated to client-side (internal normal)",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"GS(S)P Redirect Support dev mode should apply redirect when fallback GSP page is visited directly (external domain)",
"GS(S)P Redirect Support dev mode should apply redirect when fallback GSP page is visited directly (external)",
"GS(S)P Redirect Support dev mode should apply redirect when fallback GSP page is visited directly (internal dynamic)",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"GS(S)P Redirect Support dev mode should apply redirect when fallback GSP page is visited directly (internal normal)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"GS(S)P Redirect Support dev mode should apply redirect when fallback GSSP page is visited directly (external domain)",
"GS(S)P Redirect Support dev mode should apply statusCode 301 redirect when visited directly for GSSP page",
"GS(S)P Redirect Support dev mode should apply statusCode 303 redirect when visited directly for GSSP page",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"GS(S)P Redirect Support dev mode should apply temporary redirect when visited directly basePath false for GSSP page",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"GS(S)P Redirect Support dev mode should apply temporary redirect when visited directly for GSSP page",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"GS(S)P Redirect Support dev mode should not replace history of the origin page when GSP page is navigated to client-side (external)",
"GS(S)P Redirect Support dev mode should not replace history of the origin page when GSP page is navigated to client-side (internal)",
"GS(S)P Redirect Support dev mode should not replace history of the origin page when GSSP page is navigated to client-side (external)",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"GS(S)P Redirect Support dev mode should not replace history of the origin page when GSSP page is navigated to client-side (internal normal)"
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"GS(S)P Redirect Support production mode should apply permanent redirect when visited directly for GSSP page",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"GS(S)P Redirect Support production mode should apply redirect when GSP page is navigated to client-side (external)",
"GS(S)P Redirect Support production mode should apply redirect when GSP page is navigated to client-side (internal)",
"GS(S)P Redirect Support production mode should apply redirect when GSSP page is navigated to client-side (external)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"GS(S)P Redirect Support production mode should apply redirect when GSSP page is navigated to client-side (internal dynamic)",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"GS(S)P Redirect Support production mode should apply redirect when GSSP page is navigated to client-side (internal normal)",
"GS(S)P Redirect Support production mode should apply redirect when fallback GSP page is visited directly (external domain)",
"GS(S)P Redirect Support production mode should apply redirect when fallback GSP page is visited directly (external)",
"GS(S)P Redirect Support production mode should apply redirect when fallback GSP page is visited directly (internal dynamic)",
"GS(S)P Redirect Support production mode should apply redirect when fallback GSP page is visited directly (internal dynamic) 2nd visit",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"GS(S)P Redirect Support production mode should apply redirect when fallback GSP page is visited directly (internal normal)",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"GS(S)P Redirect Support production mode should apply redirect when fallback GSP page is visited directly (internal normal) 2nd visit",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"GS(S)P Redirect Support production mode should apply redirect when fallback GSSP page is visited directly (external domain)",
"GS(S)P Redirect Support production mode should apply statusCode 301 redirect when visited directly for GSSP page",
"GS(S)P Redirect Support production mode should apply statusCode 303 redirect when visited directly for GSSP page",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"GS(S)P Redirect Support production mode should apply temporary redirect when visited directly basePath false for GSSP page",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"GS(S)P Redirect Support production mode should apply temporary redirect when visited directly for GSSP page",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"GS(S)P Redirect Support production mode should error for redirect during prerendering",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"GS(S)P Redirect Support production mode should not replace history of the origin page when GSP page is navigated to client-side (external)",
"GS(S)P Redirect Support production mode should not replace history of the origin page when GSP page is navigated to client-side (internal)",
"GS(S)P Redirect Support production mode should not replace history of the origin page when GSSP page is navigated to client-side (external)",
"GS(S)P Redirect Support production mode should not replace history of the origin page when GSSP page is navigated to client-side (internal normal)"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/gssp-redirect-with-rewrites/test/index.test.js": {
"passed": [
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"getServerSideProps redirects should fallback to browser navigation for an unknown URL",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"getServerSideProps redirects should use a client-side navigation for a rewritten URL"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/gssp-redirect/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"GS(S)P Redirect Support dev mode should apply permanent redirect when visited directly for GSSP page",
"GS(S)P Redirect Support dev mode should apply redirect when GSP page is navigated to client-side (external)",
"GS(S)P Redirect Support dev mode should apply redirect when GSP page is navigated to client-side (internal)",
"GS(S)P Redirect Support dev mode should apply redirect when GSSP page is navigated to client-side (external)",
"GS(S)P Redirect Support dev mode should apply redirect when GSSP page is navigated to client-side (internal dynamic)",
"GS(S)P Redirect Support dev mode should apply redirect when GSSP page is navigated to client-side (internal normal)",
"GS(S)P Redirect Support dev mode should apply redirect when fallback GSP page is visited directly (external domain)",
"GS(S)P Redirect Support dev mode should apply redirect when fallback GSP page is visited directly (external)",
"GS(S)P Redirect Support dev mode should apply redirect when fallback GSP page is visited directly (internal dynamic)",
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"GS(S)P Redirect Support dev mode should apply redirect when fallback GSP page is visited directly (internal normal)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"GS(S)P Redirect Support dev mode should apply redirect when fallback GSSP page is visited directly (external domain)",
"GS(S)P Redirect Support dev mode should apply redirect when fallback blocking GSP page is visited directly (internal dynamic)",
"GS(S)P Redirect Support dev mode should apply redirect when fallback blocking GSP page is visited directly (internal dynamic) second visit",
"GS(S)P Redirect Support dev mode should apply redirect when fallback blocking GSP page is visited directly (internal dynamic) with revalidate",
"GS(S)P Redirect Support dev mode should apply redirect when fallback blocking GSP page is visited directly (internal dynamic) with revalidate second visit",
"GS(S)P Redirect Support dev mode should apply statusCode 301 redirect when visited directly for GSSP page",
"GS(S)P Redirect Support dev mode should apply statusCode 303 redirect when visited directly for GSSP page",
"GS(S)P Redirect Support dev mode should apply temporary redirect when visited directly for GSSP page",
"GS(S)P Redirect Support dev mode should not replace history of the origin page when GSP page is navigated to client-side (external)",
"GS(S)P Redirect Support dev mode should not replace history of the origin page when GSP page is navigated to client-side (internal)",
"GS(S)P Redirect Support dev mode should not replace history of the origin page when GSSP page is navigated to client-side (external)",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"GS(S)P Redirect Support dev mode should not replace history of the origin page when GSSP page is navigated to client-side (internal normal)"
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
],
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"GS(S)P Redirect Support production mode should apply permanent redirect when visited directly for GSSP page",
"GS(S)P Redirect Support production mode should apply redirect when GSP page is navigated to client-side (external)",
"GS(S)P Redirect Support production mode should apply redirect when GSP page is navigated to client-side (internal)",
"GS(S)P Redirect Support production mode should apply redirect when GSSP page is navigated to client-side (external)",
"GS(S)P Redirect Support production mode should apply redirect when GSSP page is navigated to client-side (internal dynamic)",
"GS(S)P Redirect Support production mode should apply redirect when GSSP page is navigated to client-side (internal normal)",
"GS(S)P Redirect Support production mode should apply redirect when fallback GSP page is visited directly (external domain)",
"GS(S)P Redirect Support production mode should apply redirect when fallback GSP page is visited directly (external)",
"GS(S)P Redirect Support production mode should apply redirect when fallback GSP page is visited directly (internal dynamic)",
"GS(S)P Redirect Support production mode should apply redirect when fallback GSP page is visited directly (internal dynamic) 2nd visit",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"GS(S)P Redirect Support production mode should apply redirect when fallback GSP page is visited directly (internal normal)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"GS(S)P Redirect Support production mode should apply redirect when fallback GSP page is visited directly (internal normal) 2nd visit",
"GS(S)P Redirect Support production mode should apply redirect when fallback GSSP page is visited directly (external domain)",
"GS(S)P Redirect Support production mode should apply redirect when fallback blocking GSP page is visited directly (internal dynamic)",
"GS(S)P Redirect Support production mode should apply redirect when fallback blocking GSP page is visited directly (internal dynamic) second visit",
"GS(S)P Redirect Support production mode should apply redirect when fallback blocking GSP page is visited directly (internal dynamic) with revalidate",
"GS(S)P Redirect Support production mode should apply redirect when fallback blocking GSP page is visited directly (internal dynamic) with revalidate second visit",
"GS(S)P Redirect Support production mode should apply statusCode 301 redirect when visited directly for GSSP page",
"GS(S)P Redirect Support production mode should apply statusCode 303 redirect when visited directly for GSSP page",
"GS(S)P Redirect Support production mode should apply temporary redirect when visited directly for GSSP page",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"GS(S)P Redirect Support production mode should error for redirect during prerendering",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"GS(S)P Redirect Support production mode should not have errors in output",
"GS(S)P Redirect Support production mode should not replace history of the origin page when GSP page is navigated to client-side (external)",
"GS(S)P Redirect Support production mode should not replace history of the origin page when GSP page is navigated to client-side (internal)",
"GS(S)P Redirect Support production mode should not replace history of the origin page when GSSP page is navigated to client-side (external)",
"GS(S)P Redirect Support production mode should not replace history of the origin page when GSSP page is navigated to client-side (internal normal)"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/handles-export-errors/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Handles Errors During Export production mode Does not crash workers"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/hashbang/test/index.test.js": {
"passed": [
"Hashbang dev mode first-line hashbang (#!) parse should work for .cjs files",
"Hashbang dev mode first-line hashbang (#!) parse should work for .js files",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Hashbang dev mode first-line hashbang (#!) parse should work for .mjs files"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Hashbang production mode first-line hashbang (#!) parse should work for .cjs files",
"Hashbang production mode first-line hashbang (#!) parse should work for .js files",
"Hashbang production mode first-line hashbang (#!) parse should work for .mjs files"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/hydrate-then-render/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"hydrate/render ordering production mode correctly measures hydrate followed by render"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/hydration/test/index.test.js": {
"passed": [
"Hydration dev mode hydrates correctly for //",
"Hydration dev mode hydrates correctly for normal page",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Hydration dev mode should be able to navigate after loading //"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"failed": [],
"pending": [
"Hydration production mode hydrates correctly for //",
"Hydration production mode hydrates correctly for normal page",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Hydration production mode should be able to navigate after loading //"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/i18n-support-base-path/test/index.test.js": {
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath dev mode should 404 for GSP pages that returned notFound",
"i18n Support basePath dev mode should 404 for GSP that returned notFound on client-transition",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"i18n Support basePath dev mode should 404 for locale prefixed public folder files",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"i18n Support basePath dev mode should 404 for locale prefixed static assets correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath dev mode should apply headers correctly",
"i18n Support basePath dev mode should apply redirects correctly",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"i18n Support basePath dev mode should apply rewrites correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath dev mode should apply trailingSlash redirect correctly",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"i18n Support basePath dev mode should generate AMP pages with all locales",
"i18n Support basePath dev mode should generate auto-export page with all locales",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath dev mode should generate fallbacks with all locales",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"i18n Support basePath dev mode should generate non-dynamic GSP page with all locales",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath dev mode should handle basePath like pathname",
"i18n Support basePath dev mode should handle locales with domain for domain example.com should handle locale do-BE",
"i18n Support basePath dev mode should handle locales with domain for domain example.com should handle locale go-BE",
"i18n Support basePath dev mode should handle locales with domain for domain example.do should handle locale do-BE",
"i18n Support basePath dev mode should handle locales with domain for domain example.do should handle locale go-BE",
"i18n Support basePath dev mode should handle navigating back to different casing of locale",
"i18n Support basePath dev mode should have correct initial query values for fallback",
"i18n Support basePath dev mode should have correct values for non-prefixed path",
"i18n Support basePath dev mode should have domainLocales available on useRouter",
"i18n Support basePath dev mode should load dynamic getServerSideProps page correctly SSR",
"i18n Support basePath dev mode should load getServerSideProps page correctly SSR",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"i18n Support basePath dev mode should load getServerSideProps page correctly SSR (default locale no prefix)",
"i18n Support basePath dev mode should load getStaticProps fallback non-prerender page another locale correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath dev mode should load getStaticProps fallback non-prerender page correctly",
"i18n Support basePath dev mode should load getStaticProps fallback non-prerender page correctly (default locale no prefix",
"i18n Support basePath dev mode should load getStaticProps fallback prerender page correctly SSR",
"i18n Support basePath dev mode should load getStaticProps fallback prerender page correctly SSR (default locale no prefix)",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"i18n Support basePath dev mode should load getStaticProps non-fallback correctly",
"i18n Support basePath dev mode should load getStaticProps non-fallback correctly another locale",
"i18n Support basePath dev mode should load getStaticProps non-fallback correctly another locale via cookie",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath dev mode should load getStaticProps page correctly SSR",
"i18n Support basePath dev mode should load getStaticProps page correctly SSR (default locale no prefix)",
"i18n Support basePath dev mode should navigate client side for default locale with no prefix",
"i18n Support basePath dev mode should navigate through history with query correctly",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"i18n Support basePath dev mode should navigate to another page and back correctly with locale",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath dev mode should navigate to auto-export dynamic page",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"i18n Support basePath dev mode should navigate to getStaticProps page and back correctly with locale",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath dev mode should navigate to page with same name as development buildId",
"i18n Support basePath dev mode should navigate with locale false correctly",
"i18n Support basePath dev mode should navigate with locale false correctly GSP",
"i18n Support basePath dev mode should navigate with locale prop correctly",
"i18n Support basePath dev mode should navigate with locale prop correctly GSP",
"i18n Support basePath dev mode should not add duplicate locale key when navigating back to root path with hash",
"i18n Support basePath dev mode should not add duplicate locale key when navigating back to root path with query params",
"i18n Support basePath dev mode should not error with similar named cookie to locale cookie",
"i18n Support basePath dev mode should not have hydration mis-match from hash",
"i18n Support basePath dev mode should not redirect to accept-lang preferred locale with locale cookie",
"i18n Support basePath dev mode should not remove locale prefix for default locale",
"i18n Support basePath dev mode should not strip locale prefix for default locale with locale domains",
"i18n Support basePath dev mode should prerender with the correct href for locale domain",
"i18n Support basePath dev mode should provide defaultLocale correctly for locale domain",
"i18n Support basePath dev mode should redirect external domain correctly",
"i18n Support basePath dev mode should redirect to correct locale domain",
"i18n Support basePath dev mode should redirect to locale prefixed route for /",
"i18n Support basePath dev mode should render 404 for blocking fallback page that returned 404",
"i18n Support basePath dev mode should render 404 for blocking fallback page that returned 404 on client transition",
"i18n Support basePath dev mode should render 404 for fallback page that returned 404",
"i18n Support basePath dev mode should render 404 for fallback page that returned 404 on client transition",
"i18n Support basePath dev mode should render the correct href with locale domains but not on a locale domain",
"i18n Support basePath dev mode should resolve auto-export dynamic route correctly",
"i18n Support basePath dev mode should resolve href correctly when dynamic route matches locale prefixed",
"i18n Support basePath dev mode should rewrite to API route correctly for do locale",
"i18n Support basePath dev mode should rewrite to API route correctly for do-BE locale",
"i18n Support basePath dev mode should rewrite to API route correctly for en locale",
"i18n Support basePath dev mode should rewrite to API route correctly for en-US locale",
"i18n Support basePath dev mode should rewrite to API route correctly for fr locale",
"i18n Support basePath dev mode should rewrite to API route correctly for fr-BE locale",
"i18n Support basePath dev mode should rewrite to API route correctly for go locale",
"i18n Support basePath dev mode should rewrite to API route correctly for go-BE locale",
"i18n Support basePath dev mode should rewrite to API route correctly for nl locale",
"i18n Support basePath dev mode should rewrite to API route correctly for nl-BE locale",
"i18n Support basePath dev mode should rewrite to API route correctly for nl-NL locale",
"i18n Support basePath dev mode should show error for redirect and notFound returned at same time",
"i18n Support basePath dev mode should transition on client properly for page that starts with locale",
"i18n Support basePath dev mode should update asPath on the client correctly",
"i18n Support basePath dev mode should use correct default locale for locale domains",
"i18n Support basePath dev mode should use default locale for / without accept-language",
"i18n Support basePath dev mode should use default locale when no locale is in href with locale false",
"i18n Support basePath dev mode should visit API route directly correctly",
"i18n Support basePath dev mode should visit dynamic API route directly correctly",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"i18n Support basePath dev mode should work with AMP first page with all locales"
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"i18n Support basePath dev mode should redirect to locale domain correctly client-side",
"i18n Support basePath dev mode should render the correct href for locale domain",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"i18n Support basePath production mode should 404 for GSP pages that returned notFound",
"i18n Support basePath production mode should 404 for GSP that returned notFound on client-transition",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support basePath production mode should 404 for locale prefixed public folder files",
"i18n Support basePath production mode should 404 for locale prefixed static assets correctly",
"i18n Support basePath production mode should add i18n config to routes-manifest",
"i18n Support basePath production mode should apply headers correctly",
"i18n Support basePath production mode should apply redirects correctly",
"i18n Support basePath production mode should apply rewrites correctly",
"i18n Support basePath production mode should apply trailingSlash redirect correctly",
"i18n Support basePath production mode should generate AMP pages with all locales",
"i18n Support basePath production mode should generate auto-export page with all locales",
"i18n Support basePath production mode should generate fallbacks with all locales",
"i18n Support basePath production mode should generate non-dynamic GSP page with all locales",
"i18n Support basePath production mode should handle basePath like pathname",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath production mode should handle fallback correctly after generating",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support basePath production mode should handle locales with domain for domain example.com should handle locale do-BE",
"i18n Support basePath production mode should handle locales with domain for domain example.com should handle locale go-BE",
"i18n Support basePath production mode should handle locales with domain for domain example.do should handle locale do-BE",
"i18n Support basePath production mode should handle locales with domain for domain example.do should handle locale go-BE",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath production mode should handle navigating back to different casing of locale",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support basePath production mode should have correct initial query values for fallback",
"i18n Support basePath production mode should have correct values for non-prefixed path",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath production mode should have domainLocales available on useRouter",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support basePath production mode should load dynamic getServerSideProps page correctly SSR",
"i18n Support basePath production mode should load getServerSideProps page correctly SSR",
"i18n Support basePath production mode should load getServerSideProps page correctly SSR (default locale no prefix)",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"i18n Support basePath production mode should load getStaticProps fallback non-prerender page another locale correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath production mode should load getStaticProps fallback non-prerender page correctly",
"i18n Support basePath production mode should load getStaticProps fallback non-prerender page correctly (default locale no prefix",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support basePath production mode should load getStaticProps fallback prerender page correctly SSR",
"i18n Support basePath production mode should load getStaticProps fallback prerender page correctly SSR (default locale no prefix)",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"i18n Support basePath production mode should load getStaticProps non-fallback correctly",
"i18n Support basePath production mode should load getStaticProps non-fallback correctly another locale",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support basePath production mode should load getStaticProps non-fallback correctly another locale via cookie",
"i18n Support basePath production mode should load getStaticProps page correctly SSR",
"i18n Support basePath production mode should load getStaticProps page correctly SSR (default locale no prefix)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath production mode should navigate client side for default locale with no prefix",
"i18n Support basePath production mode should navigate through history with query correctly",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"i18n Support basePath production mode should navigate to another page and back correctly with locale",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath production mode should navigate to auto-export dynamic page",
"i18n Support basePath production mode should navigate to getStaticProps page and back correctly with locale",
"i18n Support basePath production mode should navigate to page with same name as development buildId",
"i18n Support basePath production mode should navigate with locale false correctly",
"i18n Support basePath production mode should navigate with locale false correctly GSP",
"i18n Support basePath production mode should navigate with locale prop correctly",
"i18n Support basePath production mode should navigate with locale prop correctly GSP",
"i18n Support basePath production mode should not add duplicate locale key when navigating back to root path with hash",
"i18n Support basePath production mode should not add duplicate locale key when navigating back to root path with query params",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support basePath production mode should not contain backslashes in pages-manifest",
"i18n Support basePath production mode should not error with similar named cookie to locale cookie",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath production mode should not have hydration mis-match from hash",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support basePath production mode should not output GSP pages that returned notFound",
"i18n Support basePath production mode should not redirect to accept-lang preferred locale with locale cookie",
"i18n Support basePath production mode should not remove locale prefix for default locale",
"i18n Support basePath production mode should not strip locale prefix for default locale with locale domains",
"i18n Support basePath production mode should output correct prerender-manifest",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath production mode should preload all locales data correctly",
"i18n Support basePath production mode should prerender with the correct href for locale domain",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support basePath production mode should provide defaultLocale correctly for locale domain",
"i18n Support basePath production mode should redirect external domain correctly",
"i18n Support basePath production mode should redirect to correct locale domain",
"i18n Support basePath production mode should redirect to locale domain correctly client-side",
"i18n Support basePath production mode should redirect to locale prefixed route for /",
"i18n Support basePath production mode should render 404 for blocking fallback page that returned 404",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath production mode should render 404 for blocking fallback page that returned 404 on client transition",
"i18n Support basePath production mode should render 404 for fallback page that returned 404",
"i18n Support basePath production mode should render 404 for fallback page that returned 404 on client transition",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support basePath production mode should render the correct href for locale domain",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath production mode should render the correct href with locale domains but not on a locale domain",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support basePath production mode should resolve auto-export dynamic route correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath production mode should resolve href correctly when dynamic route matches locale prefixed",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support basePath production mode should rewrite to API route correctly for do locale",
"i18n Support basePath production mode should rewrite to API route correctly for do-BE locale",
"i18n Support basePath production mode should rewrite to API route correctly for en locale",
"i18n Support basePath production mode should rewrite to API route correctly for en-US locale",
"i18n Support basePath production mode should rewrite to API route correctly for fr locale",
"i18n Support basePath production mode should rewrite to API route correctly for fr-BE locale",
"i18n Support basePath production mode should rewrite to API route correctly for go locale",
"i18n Support basePath production mode should rewrite to API route correctly for go-BE locale",
"i18n Support basePath production mode should rewrite to API route correctly for nl locale",
"i18n Support basePath production mode should rewrite to API route correctly for nl-BE locale",
"i18n Support basePath production mode should rewrite to API route correctly for nl-NL locale",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support basePath production mode should transition on client properly for page that starts with locale",
"i18n Support basePath production mode should update asPath on the client correctly",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support basePath production mode should use correct default locale for locale domains",
"i18n Support basePath production mode should use default locale for / without accept-language",
"i18n Support basePath production mode should use default locale when no locale is in href with locale false",
"i18n Support basePath production mode should visit API route directly correctly",
"i18n Support basePath production mode should visit dynamic API route directly correctly",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"i18n Support basePath production mode should work with AMP first page with all locales",
"i18n Support basePath with localeDetection disabled production mode should have localeDetection in routes-manifest",
"i18n Support basePath with localeDetection disabled production mode should not detect locale from accept-language",
"i18n Support basePath with localeDetection disabled production mode should set locale from detected path"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/i18n-support-catchall/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support Root Catch-all dev mode should load the index route correctly CSR",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"i18n Support Root Catch-all dev mode should load the index route correctly SSR",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support Root Catch-all dev mode should navigate to other locale index and back",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support Root Catch-all dev mode should navigate to other locale page and back"
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support Root Catch-all production mode should load the index route correctly CSR",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support Root Catch-all production mode should load the index route correctly SSR",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support Root Catch-all production mode should navigate to other locale index and back",
"i18n Support Root Catch-all production mode should navigate to other locale page and back",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support Root Catch-all production mode should output prerendered index routes correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support Root Catch-all production mode should preload data correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/i18n-support-custom-error/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Custom routes i18n custom error dev mode handle custom http status maintaining locale props in custom _error page",
"Custom routes i18n custom error dev mode handle default http status maintaining locale props in custom _error page",
"Custom routes i18n custom error dev mode should localized [slug] routes render correctly",
"Custom routes i18n custom error dev mode should work also on client side routing"
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Custom routes i18n custom error production mode handle custom http status maintaining locale props in custom _error page",
"Custom routes i18n custom error production mode handle default http status maintaining locale props in custom _error page",
"Custom routes i18n custom error production mode should localized [slug] routes render correctly",
"Custom routes i18n custom error production mode should work also on client side routing"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/i18n-support-fallback-rewrite-legacy/test/index.test.js": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support dev mode should not rewrite for dynamic page",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support dev mode should not rewrite for index page"
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should not rewrite for dynamic page",
"i18n Support production mode should not rewrite for index page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/i18n-support-fallback-rewrite/test/index.test.js": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support dev mode should not rewrite for dynamic page",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support dev mode should not rewrite for index page"
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should not rewrite for dynamic page",
"i18n Support production mode should not rewrite for index page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/i18n-support-index-rewrite/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Custom routes i18n support index rewrite dev mode should handle index rewrite on client correctly",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Custom routes i18n support index rewrite dev mode should rewrite index route correctly"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Custom routes i18n support index rewrite production mode should handle index rewrite on client correctly",
"Custom routes i18n support index rewrite production mode should rewrite index route correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/i18n-support-same-page-hash-change/test/index.test.js": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Hash changes i18n dev mode should trigger hash change events",
"Hash changes i18n dev mode should update props on locale change with same hash",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Hash changes i18n dev mode should update props on locale change with same hash (dynamic page)"
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"Hash changes i18n production mode should trigger hash change events",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Hash changes i18n production mode should update props on locale change with same hash",
"Hash changes i18n production mode should update props on locale change with same hash (dynamic page)"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/i18n-support/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support dev mode should 404 for GSP pages that returned notFound",
"i18n Support dev mode should 404 for GSP that returned notFound on client-transition",
"i18n Support dev mode should 404 for locale prefixed public folder files",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"i18n Support dev mode should 404 for locale prefixed static assets correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support dev mode should apply headers correctly",
"i18n Support dev mode should apply redirects correctly",
"i18n Support dev mode should apply rewrites correctly",
"i18n Support dev mode should apply trailingSlash redirect correctly",
"i18n Support dev mode should generate AMP pages with all locales",
"i18n Support dev mode should generate auto-export page with all locales",
"i18n Support dev mode should generate fallbacks with all locales",
"i18n Support dev mode should generate non-dynamic GSP page with all locales",
"i18n Support dev mode should handle locales with domain for domain example.com should handle locale do-BE",
"i18n Support dev mode should handle locales with domain for domain example.com should handle locale go-BE",
"i18n Support dev mode should handle locales with domain for domain example.do should handle locale do-BE",
"i18n Support dev mode should handle locales with domain for domain example.do should handle locale go-BE",
"i18n Support dev mode should handle navigating back to different casing of locale",
"i18n Support dev mode should have correct initial query values for fallback",
"i18n Support dev mode should have correct values for non-prefixed path",
"i18n Support dev mode should have domainLocales available on useRouter",
"i18n Support dev mode should load dynamic getServerSideProps page correctly SSR",
"i18n Support dev mode should load getServerSideProps page correctly SSR",
"i18n Support dev mode should load getServerSideProps page correctly SSR (default locale no prefix)",
"i18n Support dev mode should load getStaticProps fallback non-prerender page another locale correctly",
"i18n Support dev mode should load getStaticProps fallback non-prerender page correctly",
"i18n Support dev mode should load getStaticProps fallback non-prerender page correctly (default locale no prefix",
"i18n Support dev mode should load getStaticProps fallback prerender page correctly SSR",
"i18n Support dev mode should load getStaticProps fallback prerender page correctly SSR (default locale no prefix)",
"i18n Support dev mode should load getStaticProps non-fallback correctly",
"i18n Support dev mode should load getStaticProps non-fallback correctly another locale",
"i18n Support dev mode should load getStaticProps non-fallback correctly another locale via cookie",
"i18n Support dev mode should load getStaticProps page correctly SSR",
"i18n Support dev mode should load getStaticProps page correctly SSR (default locale no prefix)",
"i18n Support dev mode should navigate client side for default locale with no prefix",
"i18n Support dev mode should navigate through history with query correctly",
"i18n Support dev mode should navigate to another page and back correctly with locale",
"i18n Support dev mode should navigate to auto-export dynamic page",
"i18n Support dev mode should navigate to getStaticProps page and back correctly with locale",
"i18n Support dev mode should navigate to page with same name as development buildId",
"i18n Support dev mode should navigate with locale false correctly",
"i18n Support dev mode should navigate with locale false correctly GSP",
"i18n Support dev mode should navigate with locale prop correctly",
"i18n Support dev mode should navigate with locale prop correctly GSP",
"i18n Support dev mode should not add duplicate locale key when navigating back to root path with hash",
"i18n Support dev mode should not add duplicate locale key when navigating back to root path with query params",
"i18n Support dev mode should not error with similar named cookie to locale cookie",
"i18n Support dev mode should not have hydration mis-match from hash",
"i18n Support dev mode should not redirect to accept-lang preferred locale with locale cookie",
"i18n Support dev mode should not remove locale prefix for default locale",
"i18n Support dev mode should not strip locale prefix for default locale with locale domains",
"i18n Support dev mode should prerender with the correct href for locale domain",
"i18n Support dev mode should provide defaultLocale correctly for locale domain",
"i18n Support dev mode should redirect external domain correctly",
"i18n Support dev mode should redirect to correct locale domain",
"i18n Support dev mode should redirect to locale prefixed route for /",
"i18n Support dev mode should render 404 for blocking fallback page that returned 404",
"i18n Support dev mode should render 404 for blocking fallback page that returned 404 on client transition",
"i18n Support dev mode should render 404 for fallback page that returned 404",
"i18n Support dev mode should render 404 for fallback page that returned 404 on client transition",
"i18n Support dev mode should render the correct href with locale domains but not on a locale domain",
"i18n Support dev mode should resolve auto-export dynamic route correctly",
"i18n Support dev mode should resolve href correctly when dynamic route matches locale prefixed",
"i18n Support dev mode should rewrite to API route correctly for do locale",
"i18n Support dev mode should rewrite to API route correctly for do-BE locale",
"i18n Support dev mode should rewrite to API route correctly for en locale",
"i18n Support dev mode should rewrite to API route correctly for en-US locale",
"i18n Support dev mode should rewrite to API route correctly for fr locale",
"i18n Support dev mode should rewrite to API route correctly for fr-BE locale",
"i18n Support dev mode should rewrite to API route correctly for go locale",
"i18n Support dev mode should rewrite to API route correctly for go-BE locale",
"i18n Support dev mode should rewrite to API route correctly for nl locale",
"i18n Support dev mode should rewrite to API route correctly for nl-BE locale",
"i18n Support dev mode should rewrite to API route correctly for nl-NL locale",
"i18n Support dev mode should show error for redirect and notFound returned at same time",
"i18n Support dev mode should transition on client properly for page that starts with locale",
"i18n Support dev mode should update asPath on the client correctly",
"i18n Support dev mode should use correct default locale for locale domains",
"i18n Support dev mode should use default locale for / without accept-language",
"i18n Support dev mode should use default locale when no locale is in href with locale false",
"i18n Support dev mode should visit API route directly correctly",
"i18n Support dev mode should visit dynamic API route directly correctly",
"i18n Support dev mode should work with AMP first page with all locales",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support with trailingSlash: false dev mode should redirect correctly",
"i18n Support with trailingSlash: true dev mode should navigate between pages correctly",
"i18n Support with trailingSlash: true dev mode should redirect correctly",
"i18n Support with trailingSlash: true dev mode should return 404 error for repeating locales",
"i18n Support with trailingSlash: true dev mode should serve pages correctly with locale prefix"
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"i18n Support dev mode should redirect to locale domain correctly client-side",
"i18n Support dev mode should render the correct href for locale domain",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should 404 for GSP pages that returned notFound",
"i18n Support production mode should 404 for GSP that returned notFound on client-transition",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support production mode should 404 for locale prefixed public folder files",
"i18n Support production mode should 404 for locale prefixed static assets correctly",
"i18n Support production mode should add i18n config to routes-manifest",
"i18n Support production mode should apply headers correctly",
"i18n Support production mode should apply redirects correctly",
"i18n Support production mode should apply rewrites correctly",
"i18n Support production mode should apply trailingSlash redirect correctly",
"i18n Support production mode should generate AMP pages with all locales",
"i18n Support production mode should generate auto-export page with all locales",
"i18n Support production mode should generate fallbacks with all locales",
"i18n Support production mode should generate non-dynamic GSP page with all locales",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should handle fallback correctly after generating",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support production mode should handle locales with domain for domain example.com should handle locale do-BE",
"i18n Support production mode should handle locales with domain for domain example.com should handle locale go-BE",
"i18n Support production mode should handle locales with domain for domain example.do should handle locale do-BE",
"i18n Support production mode should handle locales with domain for domain example.do should handle locale go-BE",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should handle navigating back to different casing of locale",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support production mode should have correct initial query values for fallback",
"i18n Support production mode should have correct values for non-prefixed path",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should have domainLocales available on useRouter",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support production mode should have pre-rendered /500 correctly",
"i18n Support production mode should load dynamic getServerSideProps page correctly SSR",
"i18n Support production mode should load getServerSideProps page correctly SSR",
"i18n Support production mode should load getServerSideProps page correctly SSR (default locale no prefix)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should load getStaticProps fallback non-prerender page another locale correctly",
"i18n Support production mode should load getStaticProps fallback non-prerender page correctly",
"i18n Support production mode should load getStaticProps fallback non-prerender page correctly (default locale no prefix",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support production mode should load getStaticProps fallback prerender page correctly SSR",
"i18n Support production mode should load getStaticProps fallback prerender page correctly SSR (default locale no prefix)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should load getStaticProps non-fallback correctly",
"i18n Support production mode should load getStaticProps non-fallback correctly another locale",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support production mode should load getStaticProps non-fallback correctly another locale via cookie",
"i18n Support production mode should load getStaticProps page correctly SSR",
"i18n Support production mode should load getStaticProps page correctly SSR (default locale no prefix)",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should navigate client side for default locale with no prefix",
"i18n Support production mode should navigate through history with query correctly",
"i18n Support production mode should navigate to another page and back correctly with locale",
"i18n Support production mode should navigate to auto-export dynamic page",
"i18n Support production mode should navigate to getStaticProps page and back correctly with locale",
"i18n Support production mode should navigate to page with same name as development buildId",
"i18n Support production mode should navigate with locale false correctly",
"i18n Support production mode should navigate with locale false correctly GSP",
"i18n Support production mode should navigate with locale prop correctly",
"i18n Support production mode should navigate with locale prop correctly GSP",
"i18n Support production mode should not add duplicate locale key when navigating back to root path with hash",
"i18n Support production mode should not add duplicate locale key when navigating back to root path with query params",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support production mode should not contain backslashes in pages-manifest",
"i18n Support production mode should not error with similar named cookie to locale cookie",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should not have hydration mis-match from hash",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support production mode should not output GSP pages that returned notFound",
"i18n Support production mode should not redirect to accept-lang preferred locale with locale cookie",
"i18n Support production mode should not remove locale prefix for default locale",
"i18n Support production mode should not strip locale prefix for default locale with locale domains",
"i18n Support production mode should output correct prerender-manifest",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should preload all locales data correctly",
"i18n Support production mode should prerender with the correct href for locale domain",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support production mode should provide defaultLocale correctly for locale domain",
"i18n Support production mode should redirect external domain correctly",
"i18n Support production mode should redirect to correct locale domain",
"i18n Support production mode should redirect to locale domain correctly client-side",
"i18n Support production mode should redirect to locale prefixed route for /",
"i18n Support production mode should render 404 for blocking fallback page that returned 404",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should render 404 for blocking fallback page that returned 404 on client transition",
"i18n Support production mode should render 404 for fallback page that returned 404",
"i18n Support production mode should render 404 for fallback page that returned 404 on client transition",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support production mode should render the correct href for locale domain",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should render the correct href with locale domains but not on a locale domain",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support production mode should resolve auto-export dynamic route correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should resolve href correctly when dynamic route matches locale prefixed",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support production mode should rewrite to API route correctly for do locale",
"i18n Support production mode should rewrite to API route correctly for do-BE locale",
"i18n Support production mode should rewrite to API route correctly for en locale",
"i18n Support production mode should rewrite to API route correctly for en-US locale",
"i18n Support production mode should rewrite to API route correctly for fr locale",
"i18n Support production mode should rewrite to API route correctly for fr-BE locale",
"i18n Support production mode should rewrite to API route correctly for go locale",
"i18n Support production mode should rewrite to API route correctly for go-BE locale",
"i18n Support production mode should rewrite to API route correctly for nl locale",
"i18n Support production mode should rewrite to API route correctly for nl-BE locale",
"i18n Support production mode should rewrite to API route correctly for nl-NL locale",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"i18n Support production mode should show proper error for duplicate defaultLocales",
"i18n Support production mode should show proper error for duplicate locales",
"i18n Support production mode should show proper error for invalid locale domain",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should transition on client properly for page that starts with locale",
"i18n Support production mode should update asPath on the client correctly",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support production mode should use correct default locale for locale domains",
"i18n Support production mode should use default locale for / without accept-language",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support production mode should use default locale when no locale is in href with locale false",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support production mode should visit API route directly correctly",
"i18n Support production mode should visit dynamic API route directly correctly",
"i18n Support production mode should work with AMP first page with all locales",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"i18n Support with localeDetection disabled production mode should have localeDetection in routes-manifest",
"i18n Support with localeDetection disabled production mode should ignore the invalid accept-language header",
"i18n Support with localeDetection disabled production mode should not detect locale from accept-language",
"i18n Support with localeDetection disabled production mode should set locale from detected path",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support with trailingSlash: false production mode should redirect correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"i18n Support with trailingSlash: true production mode should have correct locale domain hrefs",
"i18n Support with trailingSlash: true production mode should navigate between pages correctly",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"i18n Support with trailingSlash: true production mode should preload all locales data correctly",
"i18n Support with trailingSlash: true production mode should redirect correctly",
"i18n Support with trailingSlash: true production mode should return 404 error for repeating locales",
"i18n Support with trailingSlash: true production mode should serve pages correctly with locale prefix"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/image-generation/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Image Generation production mode should generate the image without errors"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/image-optimizer/test/content-disposition-type.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"with contentDispositionType attachment dev support with next.config.js should automatically detect image type when content-type is octet-stream",
"with contentDispositionType attachment dev support with next.config.js should compress avif smaller than webp at q=100",
"with contentDispositionType attachment dev support with next.config.js should compress avif smaller than webp at q=50",
"with contentDispositionType attachment dev support with next.config.js should compress avif smaller than webp at q=75",
"with contentDispositionType attachment dev support with next.config.js should downlevel avif format to jpeg for old Safari",
"with contentDispositionType attachment dev support with next.config.js should downlevel webp format to jpeg for old Safari",
"with contentDispositionType attachment dev support with next.config.js should emit blur svg when width is 8 in dev but not prod",
"with contentDispositionType attachment dev support with next.config.js should emit blur svg when width is less than 8 in dev but not prod",
"with contentDispositionType attachment dev support with next.config.js should error if the image file does not exist",
"with contentDispositionType attachment dev support with next.config.js should error if the resource isn't a valid image",
"with contentDispositionType attachment dev support with next.config.js should fail when domain is not defined in next.config.js",
"with contentDispositionType attachment dev support with next.config.js should fail when internal url is not an image",
"with contentDispositionType attachment dev support with next.config.js should fail when q is greater than 100",
"with contentDispositionType attachment dev support with next.config.js should fail when q is less than 1",
"with contentDispositionType attachment dev support with next.config.js should fail when q is missing",
"with contentDispositionType attachment dev support with next.config.js should fail when q is not a number",
"with contentDispositionType attachment dev support with next.config.js should fail when url fails to load an image",
"with contentDispositionType attachment dev support with next.config.js should fail when url has file protocol",
"with contentDispositionType attachment dev support with next.config.js should fail when url has ftp protocol",
"with contentDispositionType attachment dev support with next.config.js should fail when url is missing",
"with contentDispositionType attachment dev support with next.config.js should fail when w is 0",
"with contentDispositionType attachment dev support with next.config.js should fail when w is less than 0",
"with contentDispositionType attachment dev support with next.config.js should fail when w is missing",
"with contentDispositionType attachment dev support with next.config.js should fail when w is not a number",
"with contentDispositionType attachment dev support with next.config.js should fail when width is not in next.config.js",
"with contentDispositionType attachment dev support with next.config.js should handle concurrent requests",
"with contentDispositionType attachment dev support with next.config.js should handle non-ascii characters in image url",
"with contentDispositionType attachment dev support with next.config.js should maintain animated gif",
"with contentDispositionType attachment dev support with next.config.js should maintain animated png",
"with contentDispositionType attachment dev support with next.config.js should maintain animated png 2",
"with contentDispositionType attachment dev support with next.config.js should maintain animated webp",
"with contentDispositionType attachment dev support with next.config.js should maintain bmp",
"with contentDispositionType attachment dev support with next.config.js should maintain ico format",
"with contentDispositionType attachment dev support with next.config.js should maintain jpg format for old Safari",
"with contentDispositionType attachment dev support with next.config.js should maintain png format for old Safari",
"with contentDispositionType attachment dev support with next.config.js should normalize invalid status codes",
"with contentDispositionType attachment dev support with next.config.js should not allow svg with application header",
"with contentDispositionType attachment dev support with next.config.js should not allow svg with comma header",
"with contentDispositionType attachment dev support with next.config.js should not allow svg with uppercase header",
"with contentDispositionType attachment dev support with next.config.js should not allow vector svg",
"with contentDispositionType attachment dev support with next.config.js should not change the color type of a png",
"with contentDispositionType attachment dev support with next.config.js should not have sharp missing warning",
"with contentDispositionType attachment dev support with next.config.js should not have sharp outdated warning",
"with contentDispositionType attachment dev support with next.config.js should not resize if requested width is larger than original source image",
"with contentDispositionType attachment dev support with next.config.js should resize absolute url from localhost",
"with contentDispositionType attachment dev support with next.config.js should resize relative url and new Chrome accept header as avif",
"with contentDispositionType attachment dev support with next.config.js should resize relative url and old Chrome accept header as webp",
"with contentDispositionType attachment dev support with next.config.js should resize relative url and png accept header",
"with contentDispositionType attachment dev support with next.config.js should resize relative url and webp Firefox accept header",
"with contentDispositionType attachment dev support with next.config.js should resize relative url with invalid accept header as gif",
"with contentDispositionType attachment dev support with next.config.js should resize relative url with invalid accept header as png",
"with contentDispositionType attachment dev support with next.config.js should resize relative url with invalid accept header as tiff",
"with contentDispositionType attachment dev support with next.config.js should set 304 status without body when etag matches if-none-match",
"with contentDispositionType attachment dev support with next.config.js should set cache-control to immutable for static images",
"with contentDispositionType attachment dev support with next.config.js should use cache and stale-while-revalidate when query is the same for external image",
"with contentDispositionType attachment dev support with next.config.js should use cache and stale-while-revalidate when query is the same for internal image",
"with contentDispositionType attachment dev support with next.config.js should use cached image file when parameters are the same for animated gif"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"with contentDispositionType attachment dev support with next.config.js should return home page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"with contentDispositionType attachment Production Mode Server support with next.config.js should automatically detect image type when content-type is octet-stream",
"with contentDispositionType attachment Production Mode Server support with next.config.js should compress avif smaller than webp at q=100",
"with contentDispositionType attachment Production Mode Server support with next.config.js should compress avif smaller than webp at q=50",
"with contentDispositionType attachment Production Mode Server support with next.config.js should compress avif smaller than webp at q=75",
"with contentDispositionType attachment Production Mode Server support with next.config.js should downlevel avif format to jpeg for old Safari",
"with contentDispositionType attachment Production Mode Server support with next.config.js should downlevel webp format to jpeg for old Safari",
"with contentDispositionType attachment Production Mode Server support with next.config.js should emit blur svg when width is 8 in dev but not prod",
"with contentDispositionType attachment Production Mode Server support with next.config.js should emit blur svg when width is less than 8 in dev but not prod",
"with contentDispositionType attachment Production Mode Server support with next.config.js should error if the image file does not exist",
"with contentDispositionType attachment Production Mode Server support with next.config.js should error if the resource isn't a valid image",
"with contentDispositionType attachment Production Mode Server support with next.config.js should fail when domain is not defined in next.config.js",
"with contentDispositionType attachment Production Mode Server support with next.config.js should fail when internal url is not an image",
"with contentDispositionType attachment Production Mode Server support with next.config.js should fail when q is greater than 100",
"with contentDispositionType attachment Production Mode Server support with next.config.js should fail when q is less than 1",
"with contentDispositionType attachment Production Mode Server support with next.config.js should fail when q is missing",
"with contentDispositionType attachment Production Mode Server support with next.config.js should fail when q is not a number",
"with contentDispositionType attachment Production Mode Server support with next.config.js should fail when url fails to load an image",
"with contentDispositionType attachment Production Mode Server support with next.config.js should fail when url has file protocol",
"with contentDispositionType attachment Production Mode Server support with next.config.js should fail when url has ftp protocol",
"with contentDispositionType attachment Production Mode Server support with next.config.js should fail when url is missing",
"with contentDispositionType attachment Production Mode Server support with next.config.js should fail when w is 0",
"with contentDispositionType attachment Production Mode Server support with next.config.js should fail when w is less than 0",
"with contentDispositionType attachment Production Mode Server support with next.config.js should fail when w is missing",
"with contentDispositionType attachment Production Mode Server support with next.config.js should fail when w is not a number",
"with contentDispositionType attachment Production Mode Server support with next.config.js should fail when width is not in next.config.js",
"with contentDispositionType attachment Production Mode Server support with next.config.js should handle concurrent requests",
"with contentDispositionType attachment Production Mode Server support with next.config.js should handle non-ascii characters in image url",
"with contentDispositionType attachment Production Mode Server support with next.config.js should have sharp missing warning",
"with contentDispositionType attachment Production Mode Server support with next.config.js should maintain animated gif",
"with contentDispositionType attachment Production Mode Server support with next.config.js should maintain animated png",
"with contentDispositionType attachment Production Mode Server support with next.config.js should maintain animated png 2",
"with contentDispositionType attachment Production Mode Server support with next.config.js should maintain animated webp",
"with contentDispositionType attachment Production Mode Server support with next.config.js should maintain bmp",
"with contentDispositionType attachment Production Mode Server support with next.config.js should maintain ico format",
"with contentDispositionType attachment Production Mode Server support with next.config.js should maintain jpg format for old Safari",
"with contentDispositionType attachment Production Mode Server support with next.config.js should maintain png format for old Safari",
"with contentDispositionType attachment Production Mode Server support with next.config.js should normalize invalid status codes",
"with contentDispositionType attachment Production Mode Server support with next.config.js should not allow svg with application header",
"with contentDispositionType attachment Production Mode Server support with next.config.js should not allow svg with comma header",
"with contentDispositionType attachment Production Mode Server support with next.config.js should not allow svg with uppercase header",
"with contentDispositionType attachment Production Mode Server support with next.config.js should not allow vector svg",
"with contentDispositionType attachment Production Mode Server support with next.config.js should not change the color type of a png",
"with contentDispositionType attachment Production Mode Server support with next.config.js should not have sharp outdated warning",
"with contentDispositionType attachment Production Mode Server support with next.config.js should not resize if requested width is larger than original source image",
"with contentDispositionType attachment Production Mode Server support with next.config.js should resize absolute url from localhost",
"with contentDispositionType attachment Production Mode Server support with next.config.js should resize relative url and new Chrome accept header as avif",
"with contentDispositionType attachment Production Mode Server support with next.config.js should resize relative url and old Chrome accept header as webp",
"with contentDispositionType attachment Production Mode Server support with next.config.js should resize relative url and png accept header",
"with contentDispositionType attachment Production Mode Server support with next.config.js should resize relative url and webp Firefox accept header",
"with contentDispositionType attachment Production Mode Server support with next.config.js should resize relative url with invalid accept header as gif",
"with contentDispositionType attachment Production Mode Server support with next.config.js should resize relative url with invalid accept header as png",
"with contentDispositionType attachment Production Mode Server support with next.config.js should resize relative url with invalid accept header as tiff",
"with contentDispositionType attachment Production Mode Server support with next.config.js should return home page",
"with contentDispositionType attachment Production Mode Server support with next.config.js should set 304 status without body when etag matches if-none-match",
"with contentDispositionType attachment Production Mode Server support with next.config.js should set cache-control to immutable for static images",
"with contentDispositionType attachment Production Mode Server support with next.config.js should use cache and stale-while-revalidate when query is the same for external image",
"with contentDispositionType attachment Production Mode Server support with next.config.js should use cache and stale-while-revalidate when query is the same for internal image",
"with contentDispositionType attachment Production Mode Server support with next.config.js should use cached image file when parameters are the same for animated gif"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/image-optimizer/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Optimizer Server support for trailingSlash in next.config.js should return successful response for original loader",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"Image Optimizer config checks should error when assetPrefix is provided but is invalid",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Optimizer config checks should error when deviceSizes contains invalid widths",
"Image Optimizer config checks should error when domains length exceeds 50",
"Image Optimizer config checks should error when imageSizes contains invalid widths",
"Image Optimizer config checks should error when images.contentDispositionType is not valid",
"Image Optimizer config checks should error when images.contentSecurityPolicy is not a string",
"Image Optimizer config checks should error when images.dangerouslyAllowSVG is not a boolean",
"Image Optimizer config checks should error when images.formats contains invalid values",
"Image Optimizer config checks should error when images.loader and images.loaderFile are both assigned",
"Image Optimizer config checks should error when images.loader is assigned but images.path is not",
"Image Optimizer config checks should error when images.loaderFile does not exist",
"Image Optimizer config checks should error when images.minimumCacheTTL is not valid",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"Image Optimizer config checks should error when images.remotePatterns is invalid",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Optimizer config checks should error when images.unoptimized is not a boolean",
"Image Optimizer config checks should error when loader contains invalid value",
"Image Optimizer config checks should error when remotePatterns has invalid prop",
"Image Optimizer config checks should error when remotePatterns is missing hostname",
"Image Optimizer config checks should error when remotePatterns length exceeds 50",
"Image Optimizer config checks should error when sizes length exceeds 25",
"Image Optimizer dev support for dynamic blur placeholder should support width 8 per BLUR_IMG_SIZE with next dev",
"Image Optimizer dev support next.config.js cloudinary loader should 404 when loader is not default",
"Image Optimizer images.unoptimized in next.config.js should 404 when unoptimized"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Image Optimizer External rewrite support with for serving static content in images production mode should return response when image is served from an external rewrite",
"Image Optimizer Server support for headers in next.config.js production mode should not set max-age header when not matching next.config.js",
"Image Optimizer Server support for headers in next.config.js production mode should set max-age header"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/image-optimizer/test/minimum-cache-ttl.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"with minimumCacheTTL of 5 sec dev support with next.config.js should automatically detect image type when content-type is octet-stream",
"with minimumCacheTTL of 5 sec dev support with next.config.js should compress avif smaller than webp at q=100",
"with minimumCacheTTL of 5 sec dev support with next.config.js should compress avif smaller than webp at q=50",
"with minimumCacheTTL of 5 sec dev support with next.config.js should compress avif smaller than webp at q=75",
"with minimumCacheTTL of 5 sec dev support with next.config.js should downlevel avif format to jpeg for old Safari",
"with minimumCacheTTL of 5 sec dev support with next.config.js should downlevel webp format to jpeg for old Safari",
"with minimumCacheTTL of 5 sec dev support with next.config.js should emit blur svg when width is 8 in dev but not prod",
"with minimumCacheTTL of 5 sec dev support with next.config.js should emit blur svg when width is less than 8 in dev but not prod",
"with minimumCacheTTL of 5 sec dev support with next.config.js should error if the image file does not exist",
"with minimumCacheTTL of 5 sec dev support with next.config.js should error if the resource isn't a valid image",
"with minimumCacheTTL of 5 sec dev support with next.config.js should fail when domain is not defined in next.config.js",
"with minimumCacheTTL of 5 sec dev support with next.config.js should fail when internal url is not an image",
"with minimumCacheTTL of 5 sec dev support with next.config.js should fail when q is greater than 100",
"with minimumCacheTTL of 5 sec dev support with next.config.js should fail when q is less than 1",
"with minimumCacheTTL of 5 sec dev support with next.config.js should fail when q is missing",
"with minimumCacheTTL of 5 sec dev support with next.config.js should fail when q is not a number",
"with minimumCacheTTL of 5 sec dev support with next.config.js should fail when url fails to load an image",
"with minimumCacheTTL of 5 sec dev support with next.config.js should fail when url has file protocol",
"with minimumCacheTTL of 5 sec dev support with next.config.js should fail when url has ftp protocol",
"with minimumCacheTTL of 5 sec dev support with next.config.js should fail when url is missing",
"with minimumCacheTTL of 5 sec dev support with next.config.js should fail when w is 0",
"with minimumCacheTTL of 5 sec dev support with next.config.js should fail when w is less than 0",
"with minimumCacheTTL of 5 sec dev support with next.config.js should fail when w is missing",
"with minimumCacheTTL of 5 sec dev support with next.config.js should fail when w is not a number",
"with minimumCacheTTL of 5 sec dev support with next.config.js should fail when width is not in next.config.js",
"with minimumCacheTTL of 5 sec dev support with next.config.js should handle concurrent requests",
"with minimumCacheTTL of 5 sec dev support with next.config.js should handle non-ascii characters in image url",
"with minimumCacheTTL of 5 sec dev support with next.config.js should maintain animated gif",
"with minimumCacheTTL of 5 sec dev support with next.config.js should maintain animated png",
"with minimumCacheTTL of 5 sec dev support with next.config.js should maintain animated png 2",
"with minimumCacheTTL of 5 sec dev support with next.config.js should maintain animated webp",
"with minimumCacheTTL of 5 sec dev support with next.config.js should maintain bmp",
"with minimumCacheTTL of 5 sec dev support with next.config.js should maintain ico format",
"with minimumCacheTTL of 5 sec dev support with next.config.js should maintain jpg format for old Safari",
"with minimumCacheTTL of 5 sec dev support with next.config.js should maintain png format for old Safari",
"with minimumCacheTTL of 5 sec dev support with next.config.js should normalize invalid status codes",
"with minimumCacheTTL of 5 sec dev support with next.config.js should not allow svg with application header",
"with minimumCacheTTL of 5 sec dev support with next.config.js should not allow svg with comma header",
"with minimumCacheTTL of 5 sec dev support with next.config.js should not allow svg with uppercase header",
"with minimumCacheTTL of 5 sec dev support with next.config.js should not allow vector svg",
"with minimumCacheTTL of 5 sec dev support with next.config.js should not change the color type of a png",
"with minimumCacheTTL of 5 sec dev support with next.config.js should not have sharp missing warning",
"with minimumCacheTTL of 5 sec dev support with next.config.js should not have sharp outdated warning",
"with minimumCacheTTL of 5 sec dev support with next.config.js should not resize if requested width is larger than original source image",
"with minimumCacheTTL of 5 sec dev support with next.config.js should resize absolute url from localhost",
"with minimumCacheTTL of 5 sec dev support with next.config.js should resize relative url and new Chrome accept header as avif",
"with minimumCacheTTL of 5 sec dev support with next.config.js should resize relative url and old Chrome accept header as webp",
"with minimumCacheTTL of 5 sec dev support with next.config.js should resize relative url and png accept header",
"with minimumCacheTTL of 5 sec dev support with next.config.js should resize relative url and webp Firefox accept header",
"with minimumCacheTTL of 5 sec dev support with next.config.js should resize relative url with invalid accept header as gif",
"with minimumCacheTTL of 5 sec dev support with next.config.js should resize relative url with invalid accept header as png",
"with minimumCacheTTL of 5 sec dev support with next.config.js should resize relative url with invalid accept header as tiff",
"with minimumCacheTTL of 5 sec dev support with next.config.js should set 304 status without body when etag matches if-none-match",
"with minimumCacheTTL of 5 sec dev support with next.config.js should set cache-control to immutable for static images",
"with minimumCacheTTL of 5 sec dev support with next.config.js should use cache and stale-while-revalidate when query is the same for external image",
"with minimumCacheTTL of 5 sec dev support with next.config.js should use cache and stale-while-revalidate when query is the same for internal image",
"with minimumCacheTTL of 5 sec dev support with next.config.js should use cached image file when parameters are the same for animated gif"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"with minimumCacheTTL of 5 sec dev support with next.config.js should return home page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should automatically detect image type when content-type is octet-stream",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should compress avif smaller than webp at q=100",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should compress avif smaller than webp at q=50",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should compress avif smaller than webp at q=75",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should downlevel avif format to jpeg for old Safari",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should downlevel webp format to jpeg for old Safari",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should emit blur svg when width is 8 in dev but not prod",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should emit blur svg when width is less than 8 in dev but not prod",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should error if the image file does not exist",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should error if the resource isn't a valid image",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when domain is not defined in next.config.js",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when internal url is not an image",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when q is greater than 100",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when q is less than 1",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when q is missing",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when q is not a number",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when url fails to load an image",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when url has file protocol",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when url has ftp protocol",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when url is missing",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when w is 0",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when w is less than 0",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when w is missing",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when w is not a number",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should fail when width is not in next.config.js",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should handle concurrent requests",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should handle non-ascii characters in image url",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should have sharp missing warning",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should maintain animated gif",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should maintain animated png",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should maintain animated png 2",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should maintain animated webp",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should maintain bmp",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should maintain ico format",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should maintain jpg format for old Safari",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should maintain png format for old Safari",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should normalize invalid status codes",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should not allow svg with application header",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should not allow svg with comma header",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should not allow svg with uppercase header",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should not allow vector svg",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should not change the color type of a png",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should not have sharp outdated warning",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should not resize if requested width is larger than original source image",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should resize absolute url from localhost",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should resize relative url and new Chrome accept header as avif",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should resize relative url and old Chrome accept header as webp",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should resize relative url and png accept header",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should resize relative url and webp Firefox accept header",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should resize relative url with invalid accept header as gif",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should resize relative url with invalid accept header as png",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should resize relative url with invalid accept header as tiff",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should return home page",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should set 304 status without body when etag matches if-none-match",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should set cache-control to immutable for static images",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should use cache and stale-while-revalidate when query is the same for external image",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should use cache and stale-while-revalidate when query is the same for internal image",
"with minimumCacheTTL of 5 sec Production Mode Server support with next.config.js should use cached image file when parameters are the same for animated gif"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/image-optimizer/test/old-sharp.test.ts": {
"passed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
"pending": [
"with outdated sharp Production Mode Server support with next.config.js should automatically detect image type when content-type is octet-stream",
"with outdated sharp Production Mode Server support with next.config.js should compress avif smaller than webp at q=100",
"with outdated sharp Production Mode Server support with next.config.js should compress avif smaller than webp at q=50",
"with outdated sharp Production Mode Server support with next.config.js should compress avif smaller than webp at q=75",
"with outdated sharp Production Mode Server support with next.config.js should downlevel webp format to jpeg for old Safari",
"with outdated sharp Production Mode Server support with next.config.js should emit blur svg when width is 8 in dev but not prod",
"with outdated sharp Production Mode Server support with next.config.js should emit blur svg when width is less than 8 in dev but not prod",
"with outdated sharp Production Mode Server support with next.config.js should error if the image file does not exist",
"with outdated sharp Production Mode Server support with next.config.js should error if the resource isn't a valid image",
"with outdated sharp Production Mode Server support with next.config.js should fail when domain is not defined in next.config.js",
"with outdated sharp Production Mode Server support with next.config.js should fail when internal url is not an image",
"with outdated sharp Production Mode Server support with next.config.js should fail when q is greater than 100",
"with outdated sharp Production Mode Server support with next.config.js should fail when q is less than 1",
"with outdated sharp Production Mode Server support with next.config.js should fail when q is missing",
"with outdated sharp Production Mode Server support with next.config.js should fail when q is not a number",
"with outdated sharp Production Mode Server support with next.config.js should fail when url fails to load an image",
"with outdated sharp Production Mode Server support with next.config.js should fail when url has file protocol",
"with outdated sharp Production Mode Server support with next.config.js should fail when url has ftp protocol",
"with outdated sharp Production Mode Server support with next.config.js should fail when url is missing",
"with outdated sharp Production Mode Server support with next.config.js should fail when w is 0",
"with outdated sharp Production Mode Server support with next.config.js should fail when w is less than 0",
"with outdated sharp Production Mode Server support with next.config.js should fail when w is missing",
"with outdated sharp Production Mode Server support with next.config.js should fail when w is not a number",
"with outdated sharp Production Mode Server support with next.config.js should fail when width is not in next.config.js",
"with outdated sharp Production Mode Server support with next.config.js should handle concurrent requests",
update manifest (#56737) ### What? updates from daily test run Closes WEB-1766
2023-10-13 11:19:54 +02:00
"with outdated sharp Production Mode Server support with next.config.js should handle custom sharp usage",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"with outdated sharp Production Mode Server support with next.config.js should handle non-ascii characters in image url",
"with outdated sharp Production Mode Server support with next.config.js should have sharp outdated warning",
"with outdated sharp Production Mode Server support with next.config.js should maintain animated gif",
"with outdated sharp Production Mode Server support with next.config.js should maintain animated png",
"with outdated sharp Production Mode Server support with next.config.js should maintain animated png 2",
"with outdated sharp Production Mode Server support with next.config.js should maintain animated webp",
"with outdated sharp Production Mode Server support with next.config.js should maintain bmp",
"with outdated sharp Production Mode Server support with next.config.js should maintain ico format",
"with outdated sharp Production Mode Server support with next.config.js should maintain jpg format for old Safari",
"with outdated sharp Production Mode Server support with next.config.js should maintain png format for old Safari",
"with outdated sharp Production Mode Server support with next.config.js should normalize invalid status codes",
"with outdated sharp Production Mode Server support with next.config.js should not allow svg with application header",
"with outdated sharp Production Mode Server support with next.config.js should not allow svg with comma header",
"with outdated sharp Production Mode Server support with next.config.js should not allow svg with uppercase header",
"with outdated sharp Production Mode Server support with next.config.js should not allow vector svg",
"with outdated sharp Production Mode Server support with next.config.js should not have sharp missing warning",
"with outdated sharp Production Mode Server support with next.config.js should not resize if requested width is larger than original source image",
"with outdated sharp Production Mode Server support with next.config.js should resize absolute url from localhost",
"with outdated sharp Production Mode Server support with next.config.js should resize relative url and new Chrome accept header as avif",
"with outdated sharp Production Mode Server support with next.config.js should resize relative url and old Chrome accept header as webp",
"with outdated sharp Production Mode Server support with next.config.js should resize relative url and png accept header",
"with outdated sharp Production Mode Server support with next.config.js should resize relative url and webp Firefox accept header",
"with outdated sharp Production Mode Server support with next.config.js should resize relative url with invalid accept header as gif",
"with outdated sharp Production Mode Server support with next.config.js should resize relative url with invalid accept header as png",
"with outdated sharp Production Mode Server support with next.config.js should resize relative url with invalid accept header as tiff",
"with outdated sharp Production Mode Server support with next.config.js should return home page",
"with outdated sharp Production Mode Server support with next.config.js should set 304 status without body when etag matches if-none-match",
"with outdated sharp Production Mode Server support with next.config.js should set cache-control to immutable for static images",
"with outdated sharp Production Mode Server support with next.config.js should use cache and stale-while-revalidate when query is the same for external image",
"with outdated sharp Production Mode Server support with next.config.js should use cache and stale-while-revalidate when query is the same for internal image",
"with outdated sharp Production Mode Server support with next.config.js should use cached image file when parameters are the same for animated gif"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/image-optimizer/test/sharp.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"with latest sharp dev support w/o next.config.js should downlevel avif format to jpeg for old Safari",
"with latest sharp dev support w/o next.config.js should downlevel webp format to jpeg for old Safari",
"with latest sharp dev support w/o next.config.js should emit blur svg when width is 8 in dev but not prod",
"with latest sharp dev support w/o next.config.js should emit blur svg when width is less than 8 in dev but not prod",
"with latest sharp dev support w/o next.config.js should fail when domain is not defined in next.config.js",
"with latest sharp dev support w/o next.config.js should fail when internal url is not an image",
"with latest sharp dev support w/o next.config.js should fail when q is greater than 100",
"with latest sharp dev support w/o next.config.js should fail when q is less than 1",
"with latest sharp dev support w/o next.config.js should fail when q is missing",
"with latest sharp dev support w/o next.config.js should fail when q is not a number",
"with latest sharp dev support w/o next.config.js should fail when url has file protocol",
"with latest sharp dev support w/o next.config.js should fail when url has ftp protocol",
"with latest sharp dev support w/o next.config.js should fail when url is missing",
"with latest sharp dev support w/o next.config.js should fail when w is 0",
"with latest sharp dev support w/o next.config.js should fail when w is less than 0",
"with latest sharp dev support w/o next.config.js should fail when w is missing",
"with latest sharp dev support w/o next.config.js should fail when w is not a number",
"with latest sharp dev support w/o next.config.js should fail when width is not in next.config.js",
"with latest sharp dev support w/o next.config.js should handle non-ascii characters in image url",
"with latest sharp dev support w/o next.config.js should maintain animated gif",
"with latest sharp dev support w/o next.config.js should maintain animated png",
"with latest sharp dev support w/o next.config.js should maintain animated png 2",
"with latest sharp dev support w/o next.config.js should maintain animated webp",
"with latest sharp dev support w/o next.config.js should maintain bmp",
"with latest sharp dev support w/o next.config.js should maintain ico format",
"with latest sharp dev support w/o next.config.js should maintain jpg format for old Safari",
"with latest sharp dev support w/o next.config.js should maintain png format for old Safari",
"with latest sharp dev support w/o next.config.js should not allow vector svg",
"with latest sharp dev support w/o next.config.js should not have sharp missing warning",
"with latest sharp dev support w/o next.config.js should not have sharp outdated warning",
"with latest sharp dev support w/o next.config.js should not resize if requested width is larger than original source image",
"with latest sharp dev support w/o next.config.js should resize relative url and old Chrome accept header as webp",
"with latest sharp dev support w/o next.config.js should resize relative url and png accept header",
"with latest sharp dev support w/o next.config.js should resize relative url and webp Firefox accept header",
"with latest sharp dev support w/o next.config.js should resize relative url with invalid accept header as gif",
"with latest sharp dev support w/o next.config.js should resize relative url with invalid accept header as png",
"with latest sharp dev support w/o next.config.js should resize relative url with invalid accept header as tiff",
"with latest sharp dev support w/o next.config.js should set 304 status without body when etag matches if-none-match",
"with latest sharp dev support w/o next.config.js should set cache-control to immutable for static images",
"with latest sharp dev support w/o next.config.js should use cache and stale-while-revalidate when query is the same for internal image",
"with latest sharp dev support w/o next.config.js should use cached image file when parameters are the same for animated gif",
"with latest sharp dev support with next.config.js should automatically detect image type when content-type is octet-stream",
"with latest sharp dev support with next.config.js should compress avif smaller than webp at q=100",
"with latest sharp dev support with next.config.js should compress avif smaller than webp at q=50",
"with latest sharp dev support with next.config.js should compress avif smaller than webp at q=75",
"with latest sharp dev support with next.config.js should downlevel avif format to jpeg for old Safari",
"with latest sharp dev support with next.config.js should downlevel webp format to jpeg for old Safari",
"with latest sharp dev support with next.config.js should emit blur svg when width is 8 in dev but not prod",
"with latest sharp dev support with next.config.js should emit blur svg when width is less than 8 in dev but not prod",
"with latest sharp dev support with next.config.js should fail when domain is not defined in next.config.js",
"with latest sharp dev support with next.config.js should fail when internal url is not an image",
"with latest sharp dev support with next.config.js should fail when q is greater than 100",
"with latest sharp dev support with next.config.js should fail when q is less than 1",
"with latest sharp dev support with next.config.js should fail when q is missing",
"with latest sharp dev support with next.config.js should fail when q is not a number",
"with latest sharp dev support with next.config.js should fail when url has file protocol",
"with latest sharp dev support with next.config.js should fail when url has ftp protocol",
"with latest sharp dev support with next.config.js should fail when url is missing",
"with latest sharp dev support with next.config.js should fail when w is 0",
"with latest sharp dev support with next.config.js should fail when w is less than 0",
"with latest sharp dev support with next.config.js should fail when w is missing",
"with latest sharp dev support with next.config.js should fail when w is not a number",
"with latest sharp dev support with next.config.js should fail when width is not in next.config.js",
"with latest sharp dev support with next.config.js should handle concurrent requests",
"with latest sharp dev support with next.config.js should handle non-ascii characters in image url",
"with latest sharp dev support with next.config.js should maintain animated gif",
"with latest sharp dev support with next.config.js should maintain animated png",
"with latest sharp dev support with next.config.js should maintain animated png 2",
"with latest sharp dev support with next.config.js should maintain animated webp",
"with latest sharp dev support with next.config.js should maintain bmp",
"with latest sharp dev support with next.config.js should maintain ico format",
"with latest sharp dev support with next.config.js should maintain jpg format for old Safari",
"with latest sharp dev support with next.config.js should maintain png format for old Safari",
"with latest sharp dev support with next.config.js should normalize invalid status codes",
"with latest sharp dev support with next.config.js should not allow vector svg",
"with latest sharp dev support with next.config.js should not have sharp missing warning",
"with latest sharp dev support with next.config.js should not have sharp outdated warning",
"with latest sharp dev support with next.config.js should not resize if requested width is larger than original source image",
"with latest sharp dev support with next.config.js should resize absolute url from localhost",
"with latest sharp dev support with next.config.js should resize relative url and new Chrome accept header as avif",
"with latest sharp dev support with next.config.js should resize relative url and old Chrome accept header as webp",
"with latest sharp dev support with next.config.js should resize relative url and png accept header",
"with latest sharp dev support with next.config.js should resize relative url and webp Firefox accept header",
"with latest sharp dev support with next.config.js should resize relative url with invalid accept header as gif",
"with latest sharp dev support with next.config.js should resize relative url with invalid accept header as png",
"with latest sharp dev support with next.config.js should resize relative url with invalid accept header as tiff",
"with latest sharp dev support with next.config.js should set 304 status without body when etag matches if-none-match",
"with latest sharp dev support with next.config.js should set cache-control to immutable for static images",
"with latest sharp dev support with next.config.js should use cache and stale-while-revalidate when query is the same for external image",
"with latest sharp dev support with next.config.js should use cache and stale-while-revalidate when query is the same for internal image",
"with latest sharp dev support with next.config.js should use cached image file when parameters are the same for animated gif"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"with latest sharp dev support w/o next.config.js should error if the image file does not exist",
"with latest sharp dev support w/o next.config.js should error if the resource isn't a valid image",
"with latest sharp dev support w/o next.config.js should not allow svg with application header",
"with latest sharp dev support w/o next.config.js should not allow svg with comma header",
"with latest sharp dev support w/o next.config.js should not allow svg with uppercase header",
"with latest sharp dev support w/o next.config.js should return home page",
"with latest sharp dev support with next.config.js should error if the image file does not exist",
"with latest sharp dev support with next.config.js should error if the resource isn't a valid image",
"with latest sharp dev support with next.config.js should fail when url fails to load an image",
"with latest sharp dev support with next.config.js should not allow svg with application header",
"with latest sharp dev support with next.config.js should not allow svg with comma header",
"with latest sharp dev support with next.config.js should not allow svg with uppercase header",
"with latest sharp dev support with next.config.js should return home page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"with latest sharp Production Mode Server support w/o next.config.js should downlevel avif format to jpeg for old Safari",
"with latest sharp Production Mode Server support w/o next.config.js should downlevel webp format to jpeg for old Safari",
"with latest sharp Production Mode Server support w/o next.config.js should emit blur svg when width is 8 in dev but not prod",
"with latest sharp Production Mode Server support w/o next.config.js should emit blur svg when width is less than 8 in dev but not prod",
"with latest sharp Production Mode Server support w/o next.config.js should error if the image file does not exist",
"with latest sharp Production Mode Server support w/o next.config.js should error if the resource isn't a valid image",
"with latest sharp Production Mode Server support w/o next.config.js should fail when domain is not defined in next.config.js",
"with latest sharp Production Mode Server support w/o next.config.js should fail when internal url is not an image",
"with latest sharp Production Mode Server support w/o next.config.js should fail when q is greater than 100",
"with latest sharp Production Mode Server support w/o next.config.js should fail when q is less than 1",
"with latest sharp Production Mode Server support w/o next.config.js should fail when q is missing",
"with latest sharp Production Mode Server support w/o next.config.js should fail when q is not a number",
"with latest sharp Production Mode Server support w/o next.config.js should fail when url has file protocol",
"with latest sharp Production Mode Server support w/o next.config.js should fail when url has ftp protocol",
"with latest sharp Production Mode Server support w/o next.config.js should fail when url is missing",
"with latest sharp Production Mode Server support w/o next.config.js should fail when w is 0",
"with latest sharp Production Mode Server support w/o next.config.js should fail when w is less than 0",
"with latest sharp Production Mode Server support w/o next.config.js should fail when w is missing",
"with latest sharp Production Mode Server support w/o next.config.js should fail when w is not a number",
"with latest sharp Production Mode Server support w/o next.config.js should fail when width is not in next.config.js",
"with latest sharp Production Mode Server support w/o next.config.js should handle non-ascii characters in image url",
"with latest sharp Production Mode Server support w/o next.config.js should maintain animated gif",
"with latest sharp Production Mode Server support w/o next.config.js should maintain animated png",
"with latest sharp Production Mode Server support w/o next.config.js should maintain animated png 2",
"with latest sharp Production Mode Server support w/o next.config.js should maintain animated webp",
"with latest sharp Production Mode Server support w/o next.config.js should maintain bmp",
"with latest sharp Production Mode Server support w/o next.config.js should maintain ico format",
"with latest sharp Production Mode Server support w/o next.config.js should maintain jpg format for old Safari",
"with latest sharp Production Mode Server support w/o next.config.js should maintain png format for old Safari",
"with latest sharp Production Mode Server support w/o next.config.js should not allow svg with application header",
"with latest sharp Production Mode Server support w/o next.config.js should not allow svg with comma header",
"with latest sharp Production Mode Server support w/o next.config.js should not allow svg with uppercase header",
"with latest sharp Production Mode Server support w/o next.config.js should not allow vector svg",
"with latest sharp Production Mode Server support w/o next.config.js should not have sharp missing warning",
"with latest sharp Production Mode Server support w/o next.config.js should not have sharp outdated warning",
"with latest sharp Production Mode Server support w/o next.config.js should not resize if requested width is larger than original source image",
"with latest sharp Production Mode Server support w/o next.config.js should resize relative url and old Chrome accept header as webp",
"with latest sharp Production Mode Server support w/o next.config.js should resize relative url and png accept header",
"with latest sharp Production Mode Server support w/o next.config.js should resize relative url and webp Firefox accept header",
"with latest sharp Production Mode Server support w/o next.config.js should resize relative url with invalid accept header as gif",
"with latest sharp Production Mode Server support w/o next.config.js should resize relative url with invalid accept header as png",
"with latest sharp Production Mode Server support w/o next.config.js should resize relative url with invalid accept header as tiff",
"with latest sharp Production Mode Server support w/o next.config.js should return home page",
"with latest sharp Production Mode Server support w/o next.config.js should set 304 status without body when etag matches if-none-match",
"with latest sharp Production Mode Server support w/o next.config.js should set cache-control to immutable for static images",
"with latest sharp Production Mode Server support w/o next.config.js should use cache and stale-while-revalidate when query is the same for internal image",
"with latest sharp Production Mode Server support w/o next.config.js should use cached image file when parameters are the same for animated gif",
"with latest sharp Production Mode Server support with next.config.js should automatically detect image type when content-type is octet-stream",
"with latest sharp Production Mode Server support with next.config.js should compress avif smaller than webp at q=100",
"with latest sharp Production Mode Server support with next.config.js should compress avif smaller than webp at q=50",
"with latest sharp Production Mode Server support with next.config.js should compress avif smaller than webp at q=75",
"with latest sharp Production Mode Server support with next.config.js should downlevel avif format to jpeg for old Safari",
"with latest sharp Production Mode Server support with next.config.js should downlevel webp format to jpeg for old Safari",
"with latest sharp Production Mode Server support with next.config.js should emit blur svg when width is 8 in dev but not prod",
"with latest sharp Production Mode Server support with next.config.js should emit blur svg when width is less than 8 in dev but not prod",
"with latest sharp Production Mode Server support with next.config.js should error if the image file does not exist",
"with latest sharp Production Mode Server support with next.config.js should error if the resource isn't a valid image",
"with latest sharp Production Mode Server support with next.config.js should fail when domain is not defined in next.config.js",
"with latest sharp Production Mode Server support with next.config.js should fail when internal url is not an image",
"with latest sharp Production Mode Server support with next.config.js should fail when q is greater than 100",
"with latest sharp Production Mode Server support with next.config.js should fail when q is less than 1",
"with latest sharp Production Mode Server support with next.config.js should fail when q is missing",
"with latest sharp Production Mode Server support with next.config.js should fail when q is not a number",
"with latest sharp Production Mode Server support with next.config.js should fail when url fails to load an image",
"with latest sharp Production Mode Server support with next.config.js should fail when url has file protocol",
"with latest sharp Production Mode Server support with next.config.js should fail when url has ftp protocol",
"with latest sharp Production Mode Server support with next.config.js should fail when url is missing",
"with latest sharp Production Mode Server support with next.config.js should fail when w is 0",
"with latest sharp Production Mode Server support with next.config.js should fail when w is less than 0",
"with latest sharp Production Mode Server support with next.config.js should fail when w is missing",
"with latest sharp Production Mode Server support with next.config.js should fail when w is not a number",
"with latest sharp Production Mode Server support with next.config.js should fail when width is not in next.config.js",
"with latest sharp Production Mode Server support with next.config.js should handle concurrent requests",
update manifest (#56737) ### What? updates from daily test run Closes WEB-1766
2023-10-13 11:19:54 +02:00
"with latest sharp Production Mode Server support with next.config.js should handle custom sharp usage",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"with latest sharp Production Mode Server support with next.config.js should handle non-ascii characters in image url",
"with latest sharp Production Mode Server support with next.config.js should maintain animated gif",
"with latest sharp Production Mode Server support with next.config.js should maintain animated png",
"with latest sharp Production Mode Server support with next.config.js should maintain animated png 2",
"with latest sharp Production Mode Server support with next.config.js should maintain animated webp",
"with latest sharp Production Mode Server support with next.config.js should maintain bmp",
"with latest sharp Production Mode Server support with next.config.js should maintain ico format",
"with latest sharp Production Mode Server support with next.config.js should maintain jpg format for old Safari",
"with latest sharp Production Mode Server support with next.config.js should maintain png format for old Safari",
"with latest sharp Production Mode Server support with next.config.js should normalize invalid status codes",
"with latest sharp Production Mode Server support with next.config.js should not allow svg with application header",
"with latest sharp Production Mode Server support with next.config.js should not allow svg with comma header",
"with latest sharp Production Mode Server support with next.config.js should not allow svg with uppercase header",
"with latest sharp Production Mode Server support with next.config.js should not allow vector svg",
"with latest sharp Production Mode Server support with next.config.js should not have sharp missing warning",
"with latest sharp Production Mode Server support with next.config.js should not have sharp outdated warning",
"with latest sharp Production Mode Server support with next.config.js should not resize if requested width is larger than original source image",
"with latest sharp Production Mode Server support with next.config.js should resize absolute url from localhost",
"with latest sharp Production Mode Server support with next.config.js should resize relative url and new Chrome accept header as avif",
"with latest sharp Production Mode Server support with next.config.js should resize relative url and old Chrome accept header as webp",
"with latest sharp Production Mode Server support with next.config.js should resize relative url and png accept header",
"with latest sharp Production Mode Server support with next.config.js should resize relative url and webp Firefox accept header",
"with latest sharp Production Mode Server support with next.config.js should resize relative url with invalid accept header as gif",
"with latest sharp Production Mode Server support with next.config.js should resize relative url with invalid accept header as png",
"with latest sharp Production Mode Server support with next.config.js should resize relative url with invalid accept header as tiff",
"with latest sharp Production Mode Server support with next.config.js should return home page",
"with latest sharp Production Mode Server support with next.config.js should set 304 status without body when etag matches if-none-match",
"with latest sharp Production Mode Server support with next.config.js should set cache-control to immutable for static images",
"with latest sharp Production Mode Server support with next.config.js should use cache and stale-while-revalidate when query is the same for external image",
"with latest sharp Production Mode Server support with next.config.js should use cache and stale-while-revalidate when query is the same for internal image",
"with latest sharp Production Mode Server support with next.config.js should use cached image file when parameters are the same for animated gif"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/image-optimizer/test/squoosh.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"with squoosh dev support w/o next.config.js should downlevel avif format to jpeg for old Safari",
"with squoosh dev support w/o next.config.js should downlevel webp format to jpeg for old Safari",
"with squoosh dev support w/o next.config.js should emit blur svg when width is 8 in dev but not prod",
"with squoosh dev support w/o next.config.js should emit blur svg when width is less than 8 in dev but not prod",
"with squoosh dev support w/o next.config.js should error if the image file does not exist",
"with squoosh dev support w/o next.config.js should error if the resource isn't a valid image",
"with squoosh dev support w/o next.config.js should fail when domain is not defined in next.config.js",
"with squoosh dev support w/o next.config.js should fail when internal url is not an image",
"with squoosh dev support w/o next.config.js should fail when q is greater than 100",
"with squoosh dev support w/o next.config.js should fail when q is less than 1",
"with squoosh dev support w/o next.config.js should fail when q is missing",
"with squoosh dev support w/o next.config.js should fail when q is not a number",
"with squoosh dev support w/o next.config.js should fail when url has file protocol",
"with squoosh dev support w/o next.config.js should fail when url has ftp protocol",
"with squoosh dev support w/o next.config.js should fail when url is missing",
"with squoosh dev support w/o next.config.js should fail when w is 0",
"with squoosh dev support w/o next.config.js should fail when w is less than 0",
"with squoosh dev support w/o next.config.js should fail when w is missing",
"with squoosh dev support w/o next.config.js should fail when w is not a number",
"with squoosh dev support w/o next.config.js should fail when width is not in next.config.js",
"with squoosh dev support w/o next.config.js should handle non-ascii characters in image url",
"with squoosh dev support w/o next.config.js should maintain animated gif",
"with squoosh dev support w/o next.config.js should maintain animated png",
"with squoosh dev support w/o next.config.js should maintain animated png 2",
"with squoosh dev support w/o next.config.js should maintain animated webp",
"with squoosh dev support w/o next.config.js should maintain bmp",
"with squoosh dev support w/o next.config.js should maintain ico format",
"with squoosh dev support w/o next.config.js should maintain jpg format for old Safari",
"with squoosh dev support w/o next.config.js should maintain png format for old Safari",
"with squoosh dev support w/o next.config.js should not allow svg with application header",
"with squoosh dev support w/o next.config.js should not allow svg with comma header",
"with squoosh dev support w/o next.config.js should not allow svg with uppercase header",
"with squoosh dev support w/o next.config.js should not allow vector svg",
"with squoosh dev support w/o next.config.js should not change the color type of a png",
"with squoosh dev support w/o next.config.js should not have sharp missing warning",
"with squoosh dev support w/o next.config.js should not have sharp outdated warning",
"with squoosh dev support w/o next.config.js should not resize if requested width is larger than original source image",
"with squoosh dev support w/o next.config.js should resize relative url and old Chrome accept header as webp",
"with squoosh dev support w/o next.config.js should resize relative url and png accept header",
"with squoosh dev support w/o next.config.js should resize relative url and webp Firefox accept header",
"with squoosh dev support w/o next.config.js should resize relative url with invalid accept header as gif",
"with squoosh dev support w/o next.config.js should resize relative url with invalid accept header as png",
"with squoosh dev support w/o next.config.js should resize relative url with invalid accept header as tiff",
"with squoosh dev support w/o next.config.js should set 304 status without body when etag matches if-none-match",
"with squoosh dev support w/o next.config.js should set cache-control to immutable for static images",
"with squoosh dev support w/o next.config.js should use cache and stale-while-revalidate when query is the same for internal image",
"with squoosh dev support w/o next.config.js should use cached image file when parameters are the same for animated gif",
"with squoosh dev support with next.config.js should automatically detect image type when content-type is octet-stream",
"with squoosh dev support with next.config.js should compress avif smaller than webp at q=100",
"with squoosh dev support with next.config.js should compress avif smaller than webp at q=50",
"with squoosh dev support with next.config.js should compress avif smaller than webp at q=75",
"with squoosh dev support with next.config.js should downlevel avif format to jpeg for old Safari",
"with squoosh dev support with next.config.js should downlevel webp format to jpeg for old Safari",
"with squoosh dev support with next.config.js should emit blur svg when width is 8 in dev but not prod",
"with squoosh dev support with next.config.js should emit blur svg when width is less than 8 in dev but not prod",
"with squoosh dev support with next.config.js should error if the image file does not exist",
"with squoosh dev support with next.config.js should error if the resource isn't a valid image",
"with squoosh dev support with next.config.js should fail when domain is not defined in next.config.js",
"with squoosh dev support with next.config.js should fail when internal url is not an image",
"with squoosh dev support with next.config.js should fail when q is greater than 100",
"with squoosh dev support with next.config.js should fail when q is less than 1",
"with squoosh dev support with next.config.js should fail when q is missing",
"with squoosh dev support with next.config.js should fail when q is not a number",
"with squoosh dev support with next.config.js should fail when url fails to load an image",
"with squoosh dev support with next.config.js should fail when url has file protocol",
"with squoosh dev support with next.config.js should fail when url has ftp protocol",
"with squoosh dev support with next.config.js should fail when url is missing",
"with squoosh dev support with next.config.js should fail when w is 0",
"with squoosh dev support with next.config.js should fail when w is less than 0",
"with squoosh dev support with next.config.js should fail when w is missing",
"with squoosh dev support with next.config.js should fail when w is not a number",
"with squoosh dev support with next.config.js should fail when width is not in next.config.js",
"with squoosh dev support with next.config.js should handle concurrent requests",
"with squoosh dev support with next.config.js should handle non-ascii characters in image url",
"with squoosh dev support with next.config.js should maintain animated gif",
"with squoosh dev support with next.config.js should maintain animated png",
"with squoosh dev support with next.config.js should maintain animated png 2",
"with squoosh dev support with next.config.js should maintain animated webp",
"with squoosh dev support with next.config.js should maintain bmp",
"with squoosh dev support with next.config.js should maintain ico format",
"with squoosh dev support with next.config.js should maintain jpg format for old Safari",
"with squoosh dev support with next.config.js should maintain png format for old Safari",
"with squoosh dev support with next.config.js should normalize invalid status codes",
"with squoosh dev support with next.config.js should not allow svg with application header",
"with squoosh dev support with next.config.js should not allow svg with comma header",
"with squoosh dev support with next.config.js should not allow svg with uppercase header",
"with squoosh dev support with next.config.js should not allow vector svg",
"with squoosh dev support with next.config.js should not change the color type of a png",
"with squoosh dev support with next.config.js should not have sharp missing warning",
"with squoosh dev support with next.config.js should not have sharp outdated warning",
"with squoosh dev support with next.config.js should not resize if requested width is larger than original source image",
"with squoosh dev support with next.config.js should resize absolute url from localhost",
"with squoosh dev support with next.config.js should resize relative url and new Chrome accept header as avif",
"with squoosh dev support with next.config.js should resize relative url and old Chrome accept header as webp",
"with squoosh dev support with next.config.js should resize relative url and png accept header",
"with squoosh dev support with next.config.js should resize relative url and webp Firefox accept header",
"with squoosh dev support with next.config.js should resize relative url with invalid accept header as gif",
"with squoosh dev support with next.config.js should resize relative url with invalid accept header as png",
"with squoosh dev support with next.config.js should resize relative url with invalid accept header as tiff",
"with squoosh dev support with next.config.js should set 304 status without body when etag matches if-none-match",
"with squoosh dev support with next.config.js should set cache-control to immutable for static images",
"with squoosh dev support with next.config.js should use cache and stale-while-revalidate when query is the same for external image",
"with squoosh dev support with next.config.js should use cache and stale-while-revalidate when query is the same for internal image",
"with squoosh dev support with next.config.js should use cached image file when parameters are the same for animated gif"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"with squoosh dev support w/o next.config.js should return home page",
"with squoosh dev support with next.config.js should return home page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"with squoosh Production Mode Server support w/o next.config.js should downlevel avif format to jpeg for old Safari",
"with squoosh Production Mode Server support w/o next.config.js should downlevel webp format to jpeg for old Safari",
"with squoosh Production Mode Server support w/o next.config.js should emit blur svg when width is 8 in dev but not prod",
"with squoosh Production Mode Server support w/o next.config.js should emit blur svg when width is less than 8 in dev but not prod",
"with squoosh Production Mode Server support w/o next.config.js should error if the image file does not exist",
"with squoosh Production Mode Server support w/o next.config.js should error if the resource isn't a valid image",
"with squoosh Production Mode Server support w/o next.config.js should fail when domain is not defined in next.config.js",
"with squoosh Production Mode Server support w/o next.config.js should fail when internal url is not an image",
"with squoosh Production Mode Server support w/o next.config.js should fail when q is greater than 100",
"with squoosh Production Mode Server support w/o next.config.js should fail when q is less than 1",
"with squoosh Production Mode Server support w/o next.config.js should fail when q is missing",
"with squoosh Production Mode Server support w/o next.config.js should fail when q is not a number",
"with squoosh Production Mode Server support w/o next.config.js should fail when url has file protocol",
"with squoosh Production Mode Server support w/o next.config.js should fail when url has ftp protocol",
"with squoosh Production Mode Server support w/o next.config.js should fail when url is missing",
"with squoosh Production Mode Server support w/o next.config.js should fail when w is 0",
"with squoosh Production Mode Server support w/o next.config.js should fail when w is less than 0",
"with squoosh Production Mode Server support w/o next.config.js should fail when w is missing",
"with squoosh Production Mode Server support w/o next.config.js should fail when w is not a number",
"with squoosh Production Mode Server support w/o next.config.js should fail when width is not in next.config.js",
"with squoosh Production Mode Server support w/o next.config.js should handle non-ascii characters in image url",
"with squoosh Production Mode Server support w/o next.config.js should have sharp missing warning",
"with squoosh Production Mode Server support w/o next.config.js should maintain animated gif",
"with squoosh Production Mode Server support w/o next.config.js should maintain animated png",
"with squoosh Production Mode Server support w/o next.config.js should maintain animated png 2",
"with squoosh Production Mode Server support w/o next.config.js should maintain animated webp",
"with squoosh Production Mode Server support w/o next.config.js should maintain bmp",
"with squoosh Production Mode Server support w/o next.config.js should maintain ico format",
"with squoosh Production Mode Server support w/o next.config.js should maintain jpg format for old Safari",
"with squoosh Production Mode Server support w/o next.config.js should maintain png format for old Safari",
"with squoosh Production Mode Server support w/o next.config.js should not allow svg with application header",
"with squoosh Production Mode Server support w/o next.config.js should not allow svg with comma header",
"with squoosh Production Mode Server support w/o next.config.js should not allow svg with uppercase header",
"with squoosh Production Mode Server support w/o next.config.js should not allow vector svg",
"with squoosh Production Mode Server support w/o next.config.js should not change the color type of a png",
"with squoosh Production Mode Server support w/o next.config.js should not have sharp outdated warning",
"with squoosh Production Mode Server support w/o next.config.js should not resize if requested width is larger than original source image",
"with squoosh Production Mode Server support w/o next.config.js should resize relative url and old Chrome accept header as webp",
"with squoosh Production Mode Server support w/o next.config.js should resize relative url and png accept header",
"with squoosh Production Mode Server support w/o next.config.js should resize relative url and webp Firefox accept header",
"with squoosh Production Mode Server support w/o next.config.js should resize relative url with invalid accept header as gif",
"with squoosh Production Mode Server support w/o next.config.js should resize relative url with invalid accept header as png",
"with squoosh Production Mode Server support w/o next.config.js should resize relative url with invalid accept header as tiff",
"with squoosh Production Mode Server support w/o next.config.js should return home page",
"with squoosh Production Mode Server support w/o next.config.js should set 304 status without body when etag matches if-none-match",
"with squoosh Production Mode Server support w/o next.config.js should set cache-control to immutable for static images",
"with squoosh Production Mode Server support w/o next.config.js should use cache and stale-while-revalidate when query is the same for internal image",
"with squoosh Production Mode Server support w/o next.config.js should use cached image file when parameters are the same for animated gif",
"with squoosh Production Mode Server support with next.config.js should automatically detect image type when content-type is octet-stream",
"with squoosh Production Mode Server support with next.config.js should compress avif smaller than webp at q=100",
"with squoosh Production Mode Server support with next.config.js should compress avif smaller than webp at q=50",
"with squoosh Production Mode Server support with next.config.js should compress avif smaller than webp at q=75",
"with squoosh Production Mode Server support with next.config.js should downlevel avif format to jpeg for old Safari",
"with squoosh Production Mode Server support with next.config.js should downlevel webp format to jpeg for old Safari",
"with squoosh Production Mode Server support with next.config.js should emit blur svg when width is 8 in dev but not prod",
"with squoosh Production Mode Server support with next.config.js should emit blur svg when width is less than 8 in dev but not prod",
"with squoosh Production Mode Server support with next.config.js should error if the image file does not exist",
"with squoosh Production Mode Server support with next.config.js should error if the resource isn't a valid image",
"with squoosh Production Mode Server support with next.config.js should fail when domain is not defined in next.config.js",
"with squoosh Production Mode Server support with next.config.js should fail when internal url is not an image",
"with squoosh Production Mode Server support with next.config.js should fail when q is greater than 100",
"with squoosh Production Mode Server support with next.config.js should fail when q is less than 1",
"with squoosh Production Mode Server support with next.config.js should fail when q is missing",
"with squoosh Production Mode Server support with next.config.js should fail when q is not a number",
"with squoosh Production Mode Server support with next.config.js should fail when url fails to load an image",
"with squoosh Production Mode Server support with next.config.js should fail when url has file protocol",
"with squoosh Production Mode Server support with next.config.js should fail when url has ftp protocol",
"with squoosh Production Mode Server support with next.config.js should fail when url is missing",
"with squoosh Production Mode Server support with next.config.js should fail when w is 0",
"with squoosh Production Mode Server support with next.config.js should fail when w is less than 0",
"with squoosh Production Mode Server support with next.config.js should fail when w is missing",
"with squoosh Production Mode Server support with next.config.js should fail when w is not a number",
"with squoosh Production Mode Server support with next.config.js should fail when width is not in next.config.js",
"with squoosh Production Mode Server support with next.config.js should handle concurrent requests",
"with squoosh Production Mode Server support with next.config.js should handle non-ascii characters in image url",
"with squoosh Production Mode Server support with next.config.js should have sharp missing warning",
"with squoosh Production Mode Server support with next.config.js should maintain animated gif",
"with squoosh Production Mode Server support with next.config.js should maintain animated png",
"with squoosh Production Mode Server support with next.config.js should maintain animated png 2",
"with squoosh Production Mode Server support with next.config.js should maintain animated webp",
"with squoosh Production Mode Server support with next.config.js should maintain bmp",
"with squoosh Production Mode Server support with next.config.js should maintain ico format",
"with squoosh Production Mode Server support with next.config.js should maintain jpg format for old Safari",
"with squoosh Production Mode Server support with next.config.js should maintain png format for old Safari",
"with squoosh Production Mode Server support with next.config.js should normalize invalid status codes",
"with squoosh Production Mode Server support with next.config.js should not allow svg with application header",
"with squoosh Production Mode Server support with next.config.js should not allow svg with comma header",
"with squoosh Production Mode Server support with next.config.js should not allow svg with uppercase header",
"with squoosh Production Mode Server support with next.config.js should not allow vector svg",
"with squoosh Production Mode Server support with next.config.js should not change the color type of a png",
"with squoosh Production Mode Server support with next.config.js should not have sharp outdated warning",
"with squoosh Production Mode Server support with next.config.js should not resize if requested width is larger than original source image",
"with squoosh Production Mode Server support with next.config.js should resize absolute url from localhost",
"with squoosh Production Mode Server support with next.config.js should resize relative url and new Chrome accept header as avif",
"with squoosh Production Mode Server support with next.config.js should resize relative url and old Chrome accept header as webp",
"with squoosh Production Mode Server support with next.config.js should resize relative url and png accept header",
"with squoosh Production Mode Server support with next.config.js should resize relative url and webp Firefox accept header",
"with squoosh Production Mode Server support with next.config.js should resize relative url with invalid accept header as gif",
"with squoosh Production Mode Server support with next.config.js should resize relative url with invalid accept header as png",
"with squoosh Production Mode Server support with next.config.js should resize relative url with invalid accept header as tiff",
"with squoosh Production Mode Server support with next.config.js should return home page",
"with squoosh Production Mode Server support with next.config.js should set 304 status without body when etag matches if-none-match",
"with squoosh Production Mode Server support with next.config.js should set cache-control to immutable for static images",
"with squoosh Production Mode Server support with next.config.js should use cache and stale-while-revalidate when query is the same for external image",
"with squoosh Production Mode Server support with next.config.js should use cache and stale-while-revalidate when query is the same for internal image",
"with squoosh Production Mode Server support with next.config.js should use cached image file when parameters are the same for animated gif"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/import-assertion/test/index.test.js": {
feat(turbopack): port bloom filter to nexturbo (#55678) Closes WEB-1096
2023-09-28 03:00:49 +02:00
"passed": [],
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
feat(turbopack): port bloom filter to nexturbo (#55678) Closes WEB-1096
2023-09-28 03:00:49 +02:00
"flakey": [
"import-assertion dev should handle json assertions",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"production mode import-assertion prod should handle json assertions"
feat(turbopack): port bloom filter to nexturbo (#55678) Closes WEB-1096
2023-09-28 03:00:49 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/index-index/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"nested index.js dev mode should 404 on /index/index/index",
"nested index.js dev mode should client render page /",
"nested index.js dev mode should client render page /index",
"nested index.js dev mode should client render page /index/index",
"nested index.js dev mode should client render page /index/project",
"nested index.js dev mode should client render page /index/user",
"nested index.js dev mode should follow link to /",
"nested index.js dev mode should follow link to /index",
"nested index.js dev mode should follow link to /index/index",
"nested index.js dev mode should follow link to /index/project",
"nested index.js dev mode should follow link to /index/user",
"nested index.js dev mode should not find a link to /index/index/index",
"nested index.js dev mode should ssr page /",
"nested index.js dev mode should ssr page /index",
"nested index.js dev mode should ssr page /index/index",
"nested index.js dev mode should ssr page /index/project",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"nested index.js dev mode should ssr page /index/user"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"nested index.js production mode should 404 on /index/index/index",
"nested index.js production mode should client render page /",
"nested index.js production mode should client render page /index",
"nested index.js production mode should client render page /index/index",
"nested index.js production mode should client render page /index/project",
"nested index.js production mode should client render page /index/user",
"nested index.js production mode should follow link to /",
"nested index.js production mode should follow link to /index",
"nested index.js production mode should follow link to /index/index",
"nested index.js production mode should follow link to /index/project",
"nested index.js production mode should follow link to /index/user",
"nested index.js production mode should not find a link to /index/index/index",
"nested index.js production mode should ssr page /",
"nested index.js production mode should ssr page /index",
"nested index.js production mode should ssr page /index/index",
"nested index.js production mode should ssr page /index/project",
"nested index.js production mode should ssr page /index/user"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/initial-ref/test/index.test.js": {
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"passed": ["Initial Refs dev mode Has correct initial ref values"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": ["Initial Refs production mode Has correct initial ref values"],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/invalid-config-values/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Handles valid/invalid assetPrefix production mode should not error when assetPrefix is a string",
"Handles valid/invalid assetPrefix production mode should not error without usage of assetPrefix"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/invalid-custom-routes/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Errors on invalid custom routes dev mode should error during next build for invalid headers",
"Errors on invalid custom routes dev mode should error during next build for invalid redirects",
"Errors on invalid custom routes dev mode should error during next build for invalid rewrites",
"Errors on invalid custom routes dev mode should error when empty headers array is present on header item",
"Errors on invalid custom routes dev mode should error when source and destination length is exceeded",
"Errors on invalid custom routes dev mode should show formatted error for redirect source parse fail",
"Errors on invalid custom routes dev mode should show valid error when non-array is returned from headers",
"Errors on invalid custom routes dev mode should show valid error when non-array is returned from redirects",
"Errors on invalid custom routes dev mode should show valid error when non-array is returned from rewrites",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Errors on invalid custom routes dev mode should show valid error when segments not in source are used in destination"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Errors on invalid custom routes production mode should error during next build for invalid headers",
"Errors on invalid custom routes production mode should error during next build for invalid redirects",
"Errors on invalid custom routes production mode should error during next build for invalid rewrites",
"Errors on invalid custom routes production mode should error when empty headers array is present on header item",
"Errors on invalid custom routes production mode should error when source and destination length is exceeded",
"Errors on invalid custom routes production mode should show formatted error for redirect source parse fail",
"Errors on invalid custom routes production mode should show valid error when non-array is returned from headers",
"Errors on invalid custom routes production mode should show valid error when non-array is returned from redirects",
"Errors on invalid custom routes production mode should show valid error when non-array is returned from rewrites",
"Errors on invalid custom routes production mode should show valid error when segments not in source are used in destination"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/invalid-document-image-import/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Invalid static image import in _document production mode Should fail to build when disableStaticImages in next.config.js",
"Invalid static image import in _document production mode Should fail to build when no next.config.js"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/invalid-href/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Invalid hrefs dev mode does not show error when https://google.com is used as href on Link",
"Invalid hrefs dev mode does not show error when mailto: is used as href on Link",
"Invalid hrefs dev mode does not throw error when dynamic route mismatch is used on Link and params are manually provided",
"Invalid hrefs dev mode doesn't fail on invalid url",
"Invalid hrefs dev mode shows error when dynamic route mismatch is used on Link",
"Invalid hrefs dev mode shows error when internal href is used with external as",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Invalid hrefs dev mode shows warning when dynamic route mismatch is used on Link"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Invalid hrefs production mode does not show error in production when https://google.com is used as href on Link",
"Invalid hrefs production mode does not show error in production when mailto: is used as href on Link",
"Invalid hrefs production mode does not show error when internal href is used with external as",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Invalid hrefs production mode doesn't fail on invalid url",
"Invalid hrefs production mode renders a link with invalid href",
"Invalid hrefs production mode renders a link with mailto: href",
"Invalid hrefs production mode shows error when dynamic route mismatch is used on Link"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/invalid-middleware-matchers/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Errors on invalid custom middleware matchers dev mode should error during next build for invalid matchers",
"Errors on invalid custom middleware matchers dev mode should error when source length is exceeded"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Errors on invalid custom middleware matchers production mode should error during next build for invalid matchers",
"Errors on invalid custom middleware matchers production mode should error when source length is exceeded"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/invalid-multi-match/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Custom routes invalid multi-match dev mode should show error for invalid mulit-match"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"Custom routes invalid multi-match production mode should show error for invalid mulit-match"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/invalid-page-automatic-static-optimization/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Invalid Page automatic static optimization production mode Fails softly with descriptive error",
"Invalid Page automatic static optimization production mode handles non-error correctly"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/invalid-revalidate-values/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Invalid revalidate values should not show error for false revalidate value",
"Invalid revalidate values should not show error for true revalidate value",
"Invalid revalidate values should not show error initially",
"Invalid revalidate values should show error for float revalidate value",
"Invalid revalidate values should show error for null revalidate value",
"Invalid revalidate values should show error for string revalidate value"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/invalid-server-options/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Invalid server options next() called with dev as array should send warning",
"Invalid server options next() called with dev as function should send warning",
"Invalid server options next() called with dev as number should send warning",
"Invalid server options next() called with dev as object should send warning",
"Invalid server options next() called with dev as string should send warning",
"Invalid server options next() called with no parameters should throw error",
"Invalid server options next() called with null parameter should throw error",
"Invalid server options next() called with undefined parameter should throw error"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/jsconfig-baseurl/test/index.test.js": {
"passed": ["TypeScript Features default behavior should render the page"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"TypeScript Features default behavior should have correct module not found error"
],
"pending": [
"TypeScript Features should build production mode should trace correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/jsconfig-empty/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Empty JSConfig Support production mode should compile successfully"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"test/integration/jsconfig-paths-wildcard/test/index.test.js": {
fix tsconfig alias cycle (#59232) ### What? fixes https://github.com/vercel/next.js/issues/59195 fixes PACK-450 ### Why? ### How? see https://github.com/vercel/turbo/pull/6687 ### Turbopack Changes * https://github.com/vercel/turbo/pull/6627 <!-- Tobias Koppers - fix stack trace of errors --> * https://github.com/vercel/turbo/pull/6646 <!-- OJ Kwon - fix(turbo-tasks-fs): support unicode segment for glob --> * https://github.com/vercel/turbo/pull/6672 <!-- OJ Kwon - fix(ecmascript): dbg assert for the globals --> * https://github.com/vercel/turbo/pull/6687 <!-- Tobias Koppers - fix tsconfig alias cycle -->
2023-12-04 10:50:15 +01:00
"passed": [
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"jsconfig paths wildcard default behavior should resolve a wildcard alias",
"jsconfig paths without baseurl wildcard default behavior should resolve a wildcard alias"
],
fix tsconfig alias cycle (#59232) ### What? fixes https://github.com/vercel/next.js/issues/59195 fixes PACK-450 ### Why? ### How? see https://github.com/vercel/turbo/pull/6687 ### Turbopack Changes * https://github.com/vercel/turbo/pull/6627 <!-- Tobias Koppers - fix stack trace of errors --> * https://github.com/vercel/turbo/pull/6646 <!-- OJ Kwon - fix(turbo-tasks-fs): support unicode segment for glob --> * https://github.com/vercel/turbo/pull/6672 <!-- OJ Kwon - fix(ecmascript): dbg assert for the globals --> * https://github.com/vercel/turbo/pull/6687 <!-- Tobias Koppers - fix tsconfig alias cycle -->
2023-12-04 10:50:15 +01:00
"failed": [],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"pending": [],
"flakey": [],
"runtimeError": false
},
"test/integration/jsconfig-paths/test/index.test.js": {
"passed": [
"jsconfig paths default behavior should alias components",
"jsconfig paths default behavior should resolve a single matching alias",
"jsconfig paths default behavior should resolve the first item in the array first",
"jsconfig paths default behavior should resolve the second item as fallback",
"jsconfig paths without baseurl default behavior should alias components",
"jsconfig paths without baseurl default behavior should resolve a single matching alias",
"jsconfig paths without baseurl default behavior should resolve the first item in the array first",
"jsconfig paths without baseurl default behavior should resolve the second item as fallback"
],
"failed": [
"jsconfig paths default behavior should have correct module not found error",
"jsconfig paths without baseurl default behavior should have correct module not found error"
],
"pending": [
"jsconfig paths should build production mode should trace correctly",
"jsconfig paths without baseurl should build production mode should trace correctly"
],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/jsconfig/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"jsconfig.json production mode should build normally",
"jsconfig.json production mode should fail on invalid jsconfig.json"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/json-serialize-original-error/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"JSON Serialization production mode should fail with original error"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/link-ref/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Invalid hrefs dev mode should handle child ref that is a function",
"Invalid hrefs dev mode should handle child ref with React.createRef",
"Invalid hrefs dev mode should not have a race condition with a click handler",
"Invalid hrefs dev mode should not show error for class component as child of next/link",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Invalid hrefs dev mode should not show error for function component with forwardRef"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Invalid hrefs production mode should not have a race condition with a click handler",
"Invalid hrefs production mode should preload with child ref with React.createRef",
"Invalid hrefs production mode should preload with child ref with function",
"Invalid hrefs production mode should preload with forwardRef"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/link-with-encoding/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Link Component with Encoding colon should have correct parsing of url query params",
"Link Component with Encoding colon should have correct query on Router#push",
"Link Component with Encoding colon should have correct query on SSR",
"Link Component with Encoding colon should have correct query on simple client-side <Link>",
"Link Component with Encoding double quote should have correct query on Router#push",
"Link Component with Encoding double quote should have correct query on SSR",
"Link Component with Encoding double quote should have correct query on simple client-side <Link>",
"Link Component with Encoding forward slash should have correct query on Router#push",
"Link Component with Encoding forward slash should have correct query on SSR",
"Link Component with Encoding forward slash should have correct query on simple client-side <Link>",
"Link Component with Encoding percent should have correct query on Router#push",
"Link Component with Encoding percent should have correct query on SSR",
"Link Component with Encoding percent should have correct query on simple client-side <Link>",
"Link Component with Encoding spaces should have correct query on Router#push",
"Link Component with Encoding spaces should have correct query on SSR",
"Link Component with Encoding spaces should have correct query on simple client-side <Link>"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/link-with-multiple-child/test/index.test.js": {
"passed": [
"multiple child with default legacyBehavior",
"multiple child with forced legacyBehavior=false",
"single child"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/link-without-router/test/index.test.js": {
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"passed": ["Link without a router dev mode should not throw when rendered"],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Link without a router production mode should not throw when rendered"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/middleware-basic/test/index.test.js": {
"passed": ["dev mode loads a middleware"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": ["production mode loads a middleware"],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/middleware-build-errors/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Middleware validation during build production mode given a middleware building body with JSON.stringify does not throw an error",
"Middleware validation during build production mode given a middleware building response body with a variable does not throw an error",
"Middleware validation during build production mode given a middleware building response body with custom code does not throw an error",
"Middleware validation during build production mode given a middleware returning a null body builds successfully",
"Middleware validation during build production mode given a middleware returning a text body does not throw an error",
"Middleware validation during build production mode given a middleware returning a text body with NextResponse does not throw an error",
"Middleware validation during build production mode given a middleware returning an undefined body builds successfully"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/middleware-dev-update/test/index.test.js": {
"passed": [
"Middleware development errors when matcher is added sends response correctly",
"Middleware development errors when middleware is added sends response correctly",
"Middleware development errors when middleware is removed and re-added sends response correctly",
"Middleware development errors when middleware is removed sends response correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/middleware-overrides-node.js-api/test/index.test.ts": {
"passed": [
"Middleware overriding a Node.js API dev mode does not show a warning and allows overriding"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/middleware-prefetch/tests/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Middleware Production Prefetch production mode does not prefetch provided path if it will be rewritten",
"Middleware Production Prefetch production mode prefetch correctly for unexistent routes"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/middleware-src/test/index.test.js": {
"passed": [
fix(turbopack): support middleware in src (#58218) ### What? We previously marked `/src/middleware` as a missing page Fixes #42921 Closes PACK-1926 --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-11-10 14:48:20 +01:00
"Middleware in src/ and / folders dev mode loads and runs only root middleware",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Middleware in src/ folder dev mode loads an runs src middleware"
],
fix(turbopack): support middleware in src (#58218) ### What? We previously marked `/src/middleware` as a missing page Fixes #42921 Closes PACK-1926 --------- Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-11-10 14:48:20 +01:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Middleware in src/ and / folders production mode should warn about middleware on export",
"Middleware in src/ folder production mode should warn about middleware on export"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/missing-document-component-error/test/index.test.js": {
"passed": [
"Missing _document components error should detect missing Head component",
"Missing _document components error should detect missing Html component",
"Missing _document components error should detect missing Main component",
"Missing _document components error should detect missing NextScript component",
"Missing _document components error should detect multiple missing document components"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/mixed-ssg-serverprops-error/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"Mixed getStaticProps and getServerSideProps error production mode should error when exporting both getStaticPaths and getServerSideProps",
"Mixed getStaticProps and getServerSideProps error production mode should error when exporting both getStaticProps and getServerSideProps",
"Mixed getStaticProps and getServerSideProps error production mode should error when exporting getStaticPaths on a non-dynamic page",
"Mixed getStaticProps and getServerSideProps error production mode should error with getStaticProps but no default export"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-dynamic-css/test/index.test.js": {
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"passed": ["next/dynamic dev mode should load page correctly"],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": ["next/dynamic production mode should load page correctly"],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-dynamic-lazy-compilation/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"next/dynamic lazy compilation dev mode should render dynamic server rendered values before hydration",
"next/dynamic lazy compilation dev mode should render dynamic server rendered values on client mount",
"next/dynamic lazy compilation dev mode should render server value",
"next/dynamic lazy compilation production mode should render dynamic server rendered values before hydration",
"next/dynamic lazy compilation production mode should render dynamic server rendered values on client mount",
"next/dynamic lazy compilation production mode should render server value"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-dynamic/test/index.test.js": {
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"passed": [
"next/dynamic dev mode should render dynamic server rendered values on client mount",
"next/dynamic dev mode should render server value"
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
],
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"next/dynamic production mode should render dynamic server rendered values on client mount",
"next/dynamic production mode should render server value"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-legacy/asset-prefix/test/index.test.ts": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [
"Image Component assetPrefix Tests dev mode should include assetPrefix when placeholder=blur during next dev"
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"Image Component assetPrefix Tests production mode should use base64 data url with placeholder=blur during next start"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-legacy/base-path/test/index.test.ts": {
"passed": [
"Image Component basePath Tests dev mode should correctly ignore prose styles",
"Image Component basePath Tests dev mode should load the images",
"Image Component basePath Tests dev mode should show invalid src error",
"Image Component basePath Tests dev mode should show invalid src error when protocol-relative",
"Image Component basePath Tests dev mode should show missing src error",
"Image Component basePath Tests dev mode should update the image on src change",
"Image Component basePath Tests dev mode should work when using flexbox",
"Image Component basePath Tests dev mode should work with layout-fill to fill the parent and stretch with viewport",
"Image Component basePath Tests dev mode should work with layout-fill to fill the parent but NOT stretch with viewport",
"Image Component basePath Tests dev mode should work with layout-fixed so resizing window does not resize image",
"Image Component basePath Tests dev mode should work with layout-intrinsic so resizing window maintains image aspect ratio",
"Image Component basePath Tests dev mode should work with layout-responsive so resizing window maintains image aspect ratio",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Image Component basePath Tests dev mode should work with sizes and automatically use layout-responsive"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"Image Component basePath Tests production mode should correctly ignore prose styles",
"Image Component basePath Tests production mode should correctly rotate image",
"Image Component basePath Tests production mode should load the images",
"Image Component basePath Tests production mode should update the image on src change",
"Image Component basePath Tests production mode should work when using flexbox",
"Image Component basePath Tests production mode should work with layout-fill to fill the parent and stretch with viewport",
"Image Component basePath Tests production mode should work with layout-fill to fill the parent but NOT stretch with viewport",
"Image Component basePath Tests production mode should work with layout-fixed so resizing window does not resize image",
"Image Component basePath Tests production mode should work with layout-intrinsic so resizing window maintains image aspect ratio",
"Image Component basePath Tests production mode should work with layout-responsive so resizing window maintains image aspect ratio",
"Image Component basePath Tests production mode should work with sizes and automatically use layout-responsive"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-legacy/base-path/test/static.test.ts": {
"passed": [
"Static Image Component Tests for basePath dev mode Should allow an image with a static src to omit height and width",
"Static Image Component Tests for basePath dev mode Should allow provided width and height to override intrinsic",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Static Image Component Tests for basePath dev mode Should automatically provide an image height and width",
"Static Image Component Tests for basePath dev mode Should use immutable cache-control header for static import"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Static Image Component Tests for basePath dev mode Should add a blur placeholder to statically imported jpg",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Static Image Component Tests for basePath dev mode Should add a blur placeholder to statically imported png"
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
],
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Build Error Tests for basePath production mode should throw build error when import statement is used with missing file",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Static Image Component Tests for basePath production mode Should add a blur placeholder to statically imported jpg",
"Static Image Component Tests for basePath production mode Should add a blur placeholder to statically imported png",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Static Image Component Tests for basePath production mode Should allow an image with a static src to omit height and width",
"Static Image Component Tests for basePath production mode Should allow provided width and height to override intrinsic",
"Static Image Component Tests for basePath production mode Should automatically provide an image height and width",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Static Image Component Tests for basePath production mode Should use immutable cache-control header even when unoptimized",
"Static Image Component Tests for basePath production mode Should use immutable cache-control header for static import"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-legacy/basic/test/index.test.ts": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"Image Component Tests production mode Client-side Image Component Tests Client-side Errors Should not log an error when an unregistered host is used in production",
"Image Component Tests production mode Client-side Image Component Tests should NOT add a preload tag for a priority image",
"Image Component Tests production mode Client-side Image Component Tests should add a srcset based on the loader",
"Image Component Tests production mode Client-side Image Component Tests should add a srcset even with preceding slash in prop",
"Image Component Tests production mode Client-side Image Component Tests should correctly generate src even if preceding slash is included in prop",
"Image Component Tests production mode Client-side Image Component Tests should keep auto parameter if already set",
"Image Component Tests production mode Client-side Image Component Tests should keep fit parameter if already set",
"Image Component Tests production mode Client-side Image Component Tests should keep width parameter if already set",
"Image Component Tests production mode Client-side Image Component Tests should modify src with the loader",
"Image Component Tests production mode Client-side Image Component Tests should not add a srcset if unoptimized attribute present",
"Image Component Tests production mode Client-side Image Component Tests should only be loaded once if `sizes` is set",
"Image Component Tests production mode Client-side Image Component Tests should render an image tag",
"Image Component Tests production mode Client-side Image Component Tests should support passing through arbitrary attributes",
"Image Component Tests production mode Client-side Image Component Tests should support the unoptimized attribute",
"Image Component Tests production mode Client-side Image Component Tests should use imageSizes when width matches, not deviceSizes from next.config.js",
"Image Component Tests production mode Client-side Lazy Loading Tests should have loaded the first image immediately",
"Image Component Tests production mode Client-side Lazy Loading Tests should load the fifth image eagerly, without scrolling",
"Image Component Tests production mode Client-side Lazy Loading Tests should load the fourth image lazily after scrolling down",
"Image Component Tests production mode Client-side Lazy Loading Tests should load the second image after scrolling down",
"Image Component Tests production mode Client-side Lazy Loading Tests should load the sixth image, which has lazyBoundary property after scrolling down",
"Image Component Tests production mode Client-side Lazy Loading Tests should load the third image, which is unoptimized, after scrolling further down",
"Image Component Tests production mode Client-side Lazy Loading Tests should not have loaded the second image immediately",
"Image Component Tests production mode Client-side Lazy Loading Tests should not have loaded the third image after scrolling down",
"Image Component Tests production mode Client-side Lazy Loading Tests should pass through classes on a lazy loaded image",
"Image Component Tests production mode SSR Image Component Tests should add a preload tag for a priority image",
"Image Component Tests production mode SSR Image Component Tests should add a preload tag for a priority image with preceding slash",
"Image Component Tests production mode SSR Image Component Tests should add a preload tag for a priority image, with arbitrary host",
"Image Component Tests production mode SSR Image Component Tests should add a preload tag for a priority image, with quality",
"Image Component Tests production mode SSR Image Component Tests should add a srcset based on the loader",
"Image Component Tests production mode SSR Image Component Tests should add a srcset even with preceding slash in prop",
"Image Component Tests production mode SSR Image Component Tests should add data-nimg data attribute based on layout",
"Image Component Tests production mode SSR Image Component Tests should correctly generate src even if preceding slash is included in prop",
"Image Component Tests production mode SSR Image Component Tests should keep auto parameter if already set",
"Image Component Tests production mode SSR Image Component Tests should keep fit parameter if already set",
"Image Component Tests production mode SSR Image Component Tests should keep width parameter if already set",
"Image Component Tests production mode SSR Image Component Tests should modify src with the loader",
"Image Component Tests production mode SSR Image Component Tests should not add a srcset if unoptimized attribute present",
"Image Component Tests production mode SSR Image Component Tests should not create any preload tags higher up the page than CSS preload tags",
"Image Component Tests production mode SSR Image Component Tests should not pass config to custom loader prop",
"Image Component Tests production mode SSR Image Component Tests should render an image tag",
"Image Component Tests production mode SSR Image Component Tests should support passing through arbitrary attributes",
"Image Component Tests production mode SSR Image Component Tests should support the unoptimized attribute",
"Image Component Tests production mode SSR Image Component Tests should use imageSizes when width matches, not deviceSizes from next.config.js",
"Image Component Tests production mode SSR Lazy Loading Tests should have loaded the first image immediately",
"Image Component Tests production mode SSR Lazy Loading Tests should load the fifth image eagerly, without scrolling",
"Image Component Tests production mode SSR Lazy Loading Tests should load the fourth image lazily after scrolling down",
"Image Component Tests production mode SSR Lazy Loading Tests should load the second image after scrolling down",
"Image Component Tests production mode SSR Lazy Loading Tests should load the sixth image, which has lazyBoundary property after scrolling down",
"Image Component Tests production mode SSR Lazy Loading Tests should load the third image, which is unoptimized, after scrolling further down",
"Image Component Tests production mode SSR Lazy Loading Tests should not have loaded the second image immediately",
"Image Component Tests production mode SSR Lazy Loading Tests should not have loaded the third image after scrolling down",
"Image Component Tests production mode SSR Lazy Loading Tests should pass through classes on a lazy loaded image"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-legacy/custom-resolver/test/index.test.ts": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Custom Resolver Tests production mode Client-side Custom Loader Tests Should use a custom resolver for image URL",
"Custom Resolver Tests production mode Client-side Custom Loader Tests should add a srcset based on the custom resolver",
"Custom Resolver Tests production mode Client-side Custom Loader Tests should support the unoptimized attribute",
"Custom Resolver Tests production mode SSR Custom Loader Tests Should use a custom resolver for image URL",
"Custom Resolver Tests production mode SSR Custom Loader Tests should add a srcset based on the custom resolver",
"Custom Resolver Tests production mode SSR Custom Loader Tests should support the unoptimized attribute"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-legacy/default/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Component Tests dev mode should apply filter style after image loads",
"Image Component Tests dev mode should apply style inheritance for img elements but not wrapper elements",
"Image Component Tests dev mode should be valid HTML",
"Image Component Tests dev mode should callback native onError when error occured while loading image",
"Image Component Tests dev mode should callback native onLoad in most cases",
"Image Component Tests dev mode should callback onLoadingComplete when image is fully loaded",
"Image Component Tests dev mode should correctly ignore prose styles",
"Image Component Tests dev mode should emit image for next/dynamic with non ssr case",
"Image Component Tests dev mode should handle the styles prop appropriately",
"Image Component Tests dev mode should have blurry placeholder when enabled",
"Image Component Tests dev mode should initially load only two of four images using lazyroot",
"Image Component Tests dev mode should load the images",
"Image Component Tests dev mode should not pass through user-provided srcset (causing a flash)",
"Image Component Tests dev mode should not use blurry placeholder for <noscript> image",
"Image Component Tests dev mode should not warn when Image is child of p",
"Image Component Tests dev mode should not warn when svg, even if with loader prop or without",
"Image Component Tests dev mode should preload priority images",
"Image Component Tests dev mode should re-lazyload images after src changes",
"Image Component Tests dev mode should remove blurry placeholder after image loads",
"Image Component Tests dev mode should show error when not numeric string width or height",
"Image Component Tests dev mode should show error when static import and placeholder=blur and blurDataUrl is missing",
"Image Component Tests dev mode should show error when string src and placeholder=blur and blurDataURL is missing",
"Image Component Tests dev mode should show invalid src error",
"Image Component Tests dev mode should show invalid src error when protocol-relative",
"Image Component Tests dev mode should show missing src error",
"Image Component Tests dev mode should update the image on src change",
"Image Component Tests dev mode should warn at most once even after state change",
"Image Component Tests dev mode should warn when img with layout=fill is inside a container without position relative",
"Image Component Tests dev mode should warn when img with layout=responsive is inside flex container",
"Image Component Tests dev mode should warn when loader is missing width",
"Image Component Tests dev mode should warn when priority prop is missing on LCP image",
"Image Component Tests dev mode should warn when using a very small image with placeholder=blur",
"Image Component Tests dev mode should warn when using sizes with incorrect layout",
"Image Component Tests dev mode should work when using flexbox",
"Image Component Tests dev mode should work with image with blob src",
"Image Component Tests dev mode should work with layout-fill to fill the parent and stretch with viewport",
"Image Component Tests dev mode should work with layout-fill to fill the parent but NOT stretch with viewport",
"Image Component Tests dev mode should work with layout-fixed so resizing window does not resize image",
"Image Component Tests dev mode should work with layout-intrinsic so resizing window maintains image aspect ratio",
"Image Component Tests dev mode should work with layout-responsive so resizing window maintains image aspect ratio",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Image Component Tests dev mode should work with sizes and automatically use layout-responsive"
],
"failed": [],
"pending": [
"Image Component Tests production mode should apply filter style after image loads",
"Image Component Tests production mode should apply style inheritance for img elements but not wrapper elements",
"Image Component Tests production mode should be valid HTML",
"Image Component Tests production mode should callback native onError when error occured while loading image",
"Image Component Tests production mode should callback native onLoad in most cases",
"Image Component Tests production mode should callback onLoadingComplete when image is fully loaded",
"Image Component Tests production mode should correctly ignore prose styles",
"Image Component Tests production mode should correctly rotate image",
"Image Component Tests production mode should emit image for next/dynamic with non ssr case",
"Image Component Tests production mode should handle the styles prop appropriately",
"Image Component Tests production mode should have blurry placeholder when enabled",
"Image Component Tests production mode should initially load only two of four images using lazyroot",
"Image Component Tests production mode should load the images",
"Image Component Tests production mode should not create an image folder in server/chunks",
"Image Component Tests production mode should not pass through user-provided srcset (causing a flash)",
"Image Component Tests production mode should not use blurry placeholder for <noscript> image",
"Image Component Tests production mode should preload priority images",
"Image Component Tests production mode should re-lazyload images after src changes",
"Image Component Tests production mode should remove blurry placeholder after image loads",
"Image Component Tests production mode should update the image on src change",
"Image Component Tests production mode should work when using flexbox",
"Image Component Tests production mode should work with image with blob src",
"Image Component Tests production mode should work with layout-fill to fill the parent and stretch with viewport",
"Image Component Tests production mode should work with layout-fill to fill the parent but NOT stretch with viewport",
"Image Component Tests production mode should work with layout-fixed so resizing window does not resize image",
"Image Component Tests production mode should work with layout-intrinsic so resizing window maintains image aspect ratio",
"Image Component Tests production mode should work with layout-responsive so resizing window maintains image aspect ratio",
"Image Component Tests production mode should work with sizes and automatically use layout-responsive"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-legacy/default/test/static.test.ts": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"Build Error Tests production mode should throw build error when import statement is used with missing file",
"Static Image Component Tests production mode Should add a blur placeholder to statically imported jpg",
"Static Image Component Tests production mode Should add a blur placeholder to statically imported png",
"Static Image Component Tests production mode Should allow an image with a static src to omit height and width",
"Static Image Component Tests production mode Should allow provided width and height to override intrinsic",
"Static Image Component Tests production mode Should automatically provide an image height and width",
"Static Image Component Tests production mode Should use immutable cache-control header even when unoptimized",
"Static Image Component Tests production mode Should use immutable cache-control header for static import",
"Static Image Component Tests production mode should load direct imported image",
"Static Image Component Tests production mode should load staticprops imported image"
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-legacy/image-from-node-modules/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
"failed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Image Component Tests In Dev Mode should apply image config for node_modules"
],
"pending": [
"Image Component Tests In Prod Mode production mode should apply image config for node_modules"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-legacy/no-intersection-observer-fallback/test/index.test.ts": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Image Component No IntersectionObserver test production mode Client-side Lazy Loading Tests should automatically load images if observer does not exist",
"Image Component No IntersectionObserver test production mode SSR Lazy Loading Tests should automatically load images if observer does not exist"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-legacy/noscript/test/index.test.ts": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Noscript Tests production mode Noscript page source tests should use loader url for noscript img#image-with-loader src attribute",
"Noscript Tests production mode Noscript page source tests should use local API for noscript img#basic-image src attribute"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-legacy/react-virtualized/test/index.test.ts": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"react-virtualized wrapping next/legacy/image production mode should not cancel requests for images"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-legacy/svgo-webpack/test/index.test.ts": {
"passed": [],
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"svgo-webpack with Image Component development mode should print error when invalid Image usage",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"svgo-webpack with Image Component production mode should not fail to build invalid usage of the Image component"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/next-image-legacy/trailing-slash/test/index.test.ts": {
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"passed": [
"Image Component Trailing Slash Tests dev mode should include trailing slash when trailingSlash is set on config file during next dev"
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
"pending": [
"Image Component Trailing Slash Tests production mode should include trailing slash when trailingSlash is set on config file during next start"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-legacy/typescript/test/index.test.ts": {
"passed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"TypeScript Image Component development mode 2 should remove global image types when disabled (dev)",
"TypeScript Image Component development mode should have image types when enabled",
"TypeScript Image Component development mode should print error when invalid Image usage",
"TypeScript Image Component development mode should render the valid Image usage and not print error"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"TypeScript Image Component production mode should fail to build invalid usage of the Image component",
"TypeScript Image Component production mode should remove global image types when disabled"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/next-image-legacy/unicode/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
"pending": [],
"flakey": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Component Unicode Image URL dev mode should load external image with space",
"Image Component Unicode Image URL dev mode should load external unicode image",
"Image Component Unicode Image URL dev mode should load internal image with space",
"Image Component Unicode Image URL dev mode should load internal unicode image",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"Image Component Unicode Image URL dev mode should load static unicode image",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Image Component Unicode Image URL production mode should load external image with space",
"Image Component Unicode Image URL production mode should load external unicode image",
"Image Component Unicode Image URL production mode should load internal image with space",
"Image Component Unicode Image URL production mode should load internal unicode image",
"Image Component Unicode Image URL production mode should load static unicode image"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
"runtimeError": false
},
"test/integration/next-image-legacy/unoptimized/test/index.test.ts": {
"passed": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Unoptimized Image Tests dev mode should not optimize any image"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"Unoptimized Image Tests production mode should not optimize any image"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-new/app-dir/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Component Default Tests dev mode Fill-mode tests should add 100% width and height to fill images",
"Image Component Default Tests dev mode Fill-mode tests should add position styles to fill images",
"Image Component Default Tests dev mode Fill-mode tests should add position:absolute to fill images",
"Image Component Default Tests dev mode Fill-mode tests should include a data-attribute on fill images",
"Image Component Default Tests dev mode Fill-mode tests should log warnings when using fill mode incorrectly",
"Image Component Default Tests dev mode Fill-mode tests should not log incorrect warnings",
"Image Component Default Tests dev mode Fill-mode tests should not log warnings when image unmounts",
"Image Component Default Tests dev mode should apply filter style after image loads",
"Image Component Default Tests dev mode should apply style inheritance for img elements but not wrapper elements",
"Image Component Default Tests dev mode should be valid HTML",
"Image Component Default Tests dev mode should callback native onError even when error before hydration",
"Image Component Default Tests dev mode should callback native onError when error occured while loading image",
"Image Component Default Tests dev mode should callback native onLoad with sythetic event",
"Image Component Default Tests dev mode should callback onLoadingComplete when image is fully loaded",
"Image Component Default Tests dev mode should correctly ignore prose styles",
"Image Component Default Tests dev mode should emit image for next/dynamic with non ssr case",
"Image Component Default Tests dev mode should handle the styles prop appropriately",
"Image Component Default Tests dev mode should have blurry placeholder when enabled",
"Image Component Default Tests dev mode should have data url placeholder when enabled",
"Image Component Default Tests dev mode should load the images",
"Image Component Default Tests dev mode should not pass through user-provided srcset (causing a flash)",
"Image Component Default Tests dev mode should not warn when Image is child of p",
"Image Component Default Tests dev mode should not warn when data url image with fill and sizes props",
"Image Component Default Tests dev mode should not warn when svg, even if with loader prop or without",
"Image Component Default Tests dev mode should preload priority images",
"Image Component Default Tests dev mode should remove blurry placeholder after image loads",
"Image Component Default Tests dev mode should remove data url placeholder after image loads",
"Image Component Default Tests dev mode should render correct objectFit when blurDataURL and fill",
"Image Component Default Tests dev mode should render correct objectFit when data url placeholder and fill",
"Image Component Default Tests dev mode should render no wrappers or sizers",
"Image Component Default Tests dev mode should render picture via getImgProps",
"Image Component Default Tests dev mode should show empty string src error",
"Image Component Default Tests dev mode should show error when CSS position changed on fill image",
"Image Component Default Tests dev mode should show error when invalid Infinity width prop",
"Image Component Default Tests dev mode should show error when invalid height prop",
"Image Component Default Tests dev mode should show error when invalid width prop",
"Image Component Default Tests dev mode should show error when missing height prop",
"Image Component Default Tests dev mode should show error when missing width prop",
"Image Component Default Tests dev mode should show error when static import and placeholder=blur and blurDataUrl is missing",
"Image Component Default Tests dev mode should show error when string src and placeholder=blur and blurDataURL is missing",
"Image Component Default Tests dev mode should show error when width prop on fill image",
"Image Component Default Tests dev mode should show invalid src error",
"Image Component Default Tests dev mode should show invalid src error when protocol-relative",
"Image Component Default Tests dev mode should show missing alt error",
"Image Component Default Tests dev mode should show missing src error",
"Image Component Default Tests dev mode should update the image on src change",
"Image Component Default Tests dev mode should warn at most once even after state change",
"Image Component Default Tests dev mode should warn when legacy prop layout=fill",
"Image Component Default Tests dev mode should warn when legacy prop layout=responsive",
"Image Component Default Tests dev mode should warn when loader is missing width",
"Image Component Default Tests dev mode should warn when priority prop is missing on LCP image",
"Image Component Default Tests dev mode should warn when using a very small image with placeholder=blur",
"Image Component Default Tests dev mode should work when using flexbox",
"Image Component Default Tests dev mode should work with image with blob src",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Image Component Default Tests dev mode should work with sizes and automatically use responsive srcset"
],
"failed": [
"Image Component Default Tests dev mode should lazy load with placeholder=blur"
],
"pending": [
"Image Component Default Tests production mode Fill-mode tests should add 100% width and height to fill images",
"Image Component Default Tests production mode Fill-mode tests should add position styles to fill images",
"Image Component Default Tests production mode Fill-mode tests should add position:absolute to fill images",
"Image Component Default Tests production mode Fill-mode tests should include a data-attribute on fill images",
"Image Component Default Tests production mode should apply filter style after image loads",
"Image Component Default Tests production mode should apply style inheritance for img elements but not wrapper elements",
"Image Component Default Tests production mode should be valid HTML",
"Image Component Default Tests production mode should callback native onError even when error before hydration",
"Image Component Default Tests production mode should callback native onError when error occured while loading image",
"Image Component Default Tests production mode should callback native onLoad with sythetic event",
"Image Component Default Tests production mode should callback onLoadingComplete when image is fully loaded",
"Image Component Default Tests production mode should correctly ignore prose styles",
"Image Component Default Tests production mode should correctly rotate image",
"Image Component Default Tests production mode should emit image for next/dynamic with non ssr case",
"Image Component Default Tests production mode should handle the styles prop appropriately",
"Image Component Default Tests production mode should have blurry placeholder when enabled",
"Image Component Default Tests production mode should have data url placeholder when enabled",
"Image Component Default Tests production mode should lazy load with placeholder=blur",
"Image Component Default Tests production mode should load the images",
"Image Component Default Tests production mode should not create an image folder in server/chunks",
"Image Component Default Tests production mode should not pass through user-provided srcset (causing a flash)",
"Image Component Default Tests production mode should preload priority images",
"Image Component Default Tests production mode should remove blurry placeholder after image loads",
"Image Component Default Tests production mode should remove data url placeholder after image loads",
"Image Component Default Tests production mode should render as unoptimized with empty string src prop",
"Image Component Default Tests production mode should render as unoptimized with missing src prop",
"Image Component Default Tests production mode should render correct objectFit when blurDataURL and fill",
"Image Component Default Tests production mode should render correct objectFit when data url placeholder and fill",
"Image Component Default Tests production mode should render no wrappers or sizers",
"Image Component Default Tests production mode should render picture via getImgProps",
"Image Component Default Tests production mode should update the image on src change",
"Image Component Default Tests production mode should warn when legacy prop layout=fill",
"Image Component Default Tests production mode should warn when legacy prop layout=responsive",
"Image Component Default Tests production mode should work when using flexbox",
"Image Component Default Tests production mode should work with image with blob src",
"Image Component Default Tests production mode should work with sizes and automatically use responsive srcset"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-new/app-dir/test/static.test.ts": {
"passed": [
"Static Image Component Tests dev mode Should allow an image with a static src to omit height and width",
"Static Image Component Tests dev mode Should automatically provide an image height and width",
"Static Image Component Tests dev mode should add a data URL placeholder to an image",
"Static Image Component Tests dev mode should add placeholder even when blurDataURL aspect ratio does not match width/height ratio",
"Static Image Component Tests dev mode should add placeholder with blurDataURL and fill",
"Static Image Component Tests dev mode should load direct imported image",
"Static Image Component Tests dev mode should use height prop to adjust both width and height",
"Static Image Component Tests dev mode should use width and height prop to override import",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Static Image Component Tests dev mode should use width prop to adjust both width and height"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Static Image Component Tests dev mode should add a blur placeholder a statically imported jpg",
"Static Image Component Tests dev mode should add a blur placeholder a statically imported png",
"Static Image Component Tests dev mode should add a blur placeholder a statically imported png with fill",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Static Image Component Tests dev mode should have <head> containing <meta name=\"viewport\"> followed by <link rel=\"preload\"> for priority image"
],
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Build Error Tests production mode should throw build error when import statement is used with missing file",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Static Image Component Tests production mode Should allow an image with a static src to omit height and width",
"Static Image Component Tests production mode Should automatically provide an image height and width",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Static Image Component Tests production mode Should use immutable cache-control header even when unoptimized",
"Static Image Component Tests production mode Should use immutable cache-control header for static import",
"Static Image Component Tests production mode should add a blur placeholder a statically imported jpg",
"Static Image Component Tests production mode should add a blur placeholder a statically imported png",
"Static Image Component Tests production mode should add a blur placeholder a statically imported png with fill",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Static Image Component Tests production mode should add a data URL placeholder to an image",
"Static Image Component Tests production mode should add placeholder even when blurDataURL aspect ratio does not match width/height ratio",
"Static Image Component Tests production mode should add placeholder with blurDataURL and fill",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Static Image Component Tests production mode should have <head> containing <meta name=\"viewport\"> followed by <link rel=\"preload\"> for priority image",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Static Image Component Tests production mode should load direct imported image",
"Static Image Component Tests production mode should use height prop to adjust both width and height",
"Static Image Component Tests production mode should use width and height prop to override import",
"Static Image Component Tests production mode should use width prop to adjust both width and height"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-new/asset-prefix/test/index.test.js": {
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"passed": [
"Image Component assetPrefix Tests dev mode should not log a deprecation warning about using `images.domains`"
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Component assetPrefix Tests dev mode should include assetPrefix when placeholder=blur during next dev"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"Image Component assetPrefix Tests production mode should not log a deprecation warning about using `images.domains`",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Image Component assetPrefix Tests production mode should use base64 data url with placeholder=blur during next start"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/next-image-new/base-path/test/index.test.js": {
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Component basePath Tests dev mode should correctly ignore prose styles",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Image Component basePath Tests dev mode should load the images",
"Image Component basePath Tests dev mode should show invalid src error",
"Image Component basePath Tests dev mode should show invalid src error when protocol-relative",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Component basePath Tests dev mode should show missing src error",
"Image Component basePath Tests dev mode should update the image on src change",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Image Component basePath Tests dev mode should work when using flexbox"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"Image Component basePath Tests production mode should correctly ignore prose styles",
"Image Component basePath Tests production mode should load the images",
"Image Component basePath Tests production mode should update the image on src change",
"Image Component basePath Tests production mode should work when using flexbox"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-new/base-path/test/static.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Static Image Component Tests for basePath dev mode Should allow an image with a static src to omit height and width",
"Static Image Component Tests for basePath dev mode Should automatically provide an image height and width",
"Static Image Component Tests for basePath dev mode should add a data URL placeholder to an image",
"Static Image Component Tests for basePath dev mode should use height prop to adjust both width and height",
"Static Image Component Tests for basePath dev mode should use width and height prop to override import",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Static Image Component Tests for basePath dev mode should use width prop to adjust both width and height"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Static Image Component Tests for basePath dev mode should add a blur placeholder a statically imported jpg",
"Static Image Component Tests for basePath dev mode should add a blur placeholder a statically imported png",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Static Image Component Tests for basePath dev mode should have <head> containing <meta name=\"viewport\"> followed by <link rel=\"preload\"> for priority image"
],
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Build Error Tests production mode should throw build error when import statement is used with missing file",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Static Image Component Tests for basePath production mode Should allow an image with a static src to omit height and width",
"Static Image Component Tests for basePath production mode Should automatically provide an image height and width",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Static Image Component Tests for basePath production mode Should use immutable cache-control header even when unoptimized",
"Static Image Component Tests for basePath production mode Should use immutable cache-control header for static import",
"Static Image Component Tests for basePath production mode should add a blur placeholder a statically imported jpg",
"Static Image Component Tests for basePath production mode should add a blur placeholder a statically imported png",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Static Image Component Tests for basePath production mode should add a data URL placeholder to an image",
"Static Image Component Tests for basePath production mode should have <head> containing <meta name=\"viewport\"> followed by <link rel=\"preload\"> for priority image",
"Static Image Component Tests for basePath production mode should use height prop to adjust both width and height",
"Static Image Component Tests for basePath production mode should use width and height prop to override import",
"Static Image Component Tests for basePath production mode should use width prop to adjust both width and height"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-new/both-basepath-trailingslash/test/index.test.ts": {
"passed": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Image Component basePath + trailingSlash Tests dev mode should correctly load image src from string"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Image Component basePath + trailingSlash Tests dev mode should correctly load image src from import"
],
"pending": [
"Image Component basePath + trailingSlash Tests production mode should correctly load image src from import",
"Image Component basePath + trailingSlash Tests production mode should correctly load image src from string"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/next-image-new/default/test/index.test.ts": {
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Component Default Tests dev mode Fill-mode tests should add 100% width and height to fill images",
"Image Component Default Tests dev mode Fill-mode tests should add position styles to fill images",
"Image Component Default Tests dev mode Fill-mode tests should add position:absolute to fill images",
"Image Component Default Tests dev mode Fill-mode tests should include a data-attribute on fill images",
"Image Component Default Tests dev mode Fill-mode tests should log warnings when using fill mode incorrectly",
"Image Component Default Tests dev mode Fill-mode tests should not log incorrect warnings",
"Image Component Default Tests dev mode Fill-mode tests should not log warnings when image unmounts",
"Image Component Default Tests dev mode should apply filter style after image loads",
"Image Component Default Tests dev mode should apply style inheritance for img elements but not wrapper elements",
"Image Component Default Tests dev mode should be valid HTML",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Image Component Default Tests dev mode should callback native onError even when error before hydration",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Component Default Tests dev mode should callback native onError when error occured while loading image",
"Image Component Default Tests dev mode should callback native onLoad with sythetic event",
"Image Component Default Tests dev mode should callback onLoadingComplete when image is fully loaded",
"Image Component Default Tests dev mode should correctly ignore prose styles",
"Image Component Default Tests dev mode should emit image for next/dynamic with non ssr case",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Image Component Default Tests dev mode should handle the styles prop appropriately",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Component Default Tests dev mode should have blurry placeholder when enabled",
"Image Component Default Tests dev mode should have data url placeholder when enabled",
"Image Component Default Tests dev mode should load the images",
"Image Component Default Tests dev mode should not pass through user-provided srcset (causing a flash)",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Image Component Default Tests dev mode should not warn when Image is child of p",
"Image Component Default Tests dev mode should not warn when data url image with fill and sizes props",
"Image Component Default Tests dev mode should not warn when svg, even if with loader prop or without",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Component Default Tests dev mode should preload priority images",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Image Component Default Tests dev mode should remove blurry placeholder after image loads",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Component Default Tests dev mode should remove data url placeholder after image loads",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Image Component Default Tests dev mode should render correct objectFit when blurDataURL and fill",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Component Default Tests dev mode should render correct objectFit when data url placeholder and fill",
"Image Component Default Tests dev mode should render no wrappers or sizers",
"Image Component Default Tests dev mode should render picture via getImgProps",
"Image Component Default Tests dev mode should show empty string src error",
"Image Component Default Tests dev mode should show error when CSS position changed on fill image",
"Image Component Default Tests dev mode should show error when invalid Infinity width prop",
"Image Component Default Tests dev mode should show error when invalid height prop",
"Image Component Default Tests dev mode should show error when invalid width prop",
"Image Component Default Tests dev mode should show error when missing height prop",
"Image Component Default Tests dev mode should show error when missing width prop",
"Image Component Default Tests dev mode should show error when static import and placeholder=blur and blurDataUrl is missing",
"Image Component Default Tests dev mode should show error when string src and placeholder=blur and blurDataURL is missing",
"Image Component Default Tests dev mode should show error when width prop on fill image",
"Image Component Default Tests dev mode should show invalid src error",
"Image Component Default Tests dev mode should show invalid src error when protocol-relative",
"Image Component Default Tests dev mode should show missing alt error",
"Image Component Default Tests dev mode should show missing src error",
"Image Component Default Tests dev mode should update the image on src change",
"Image Component Default Tests dev mode should warn at most once even after state change",
"Image Component Default Tests dev mode should warn when legacy prop layout=fill",
"Image Component Default Tests dev mode should warn when legacy prop layout=responsive",
"Image Component Default Tests dev mode should warn when loader is missing width",
"Image Component Default Tests dev mode should warn when priority prop is missing on LCP image",
"Image Component Default Tests dev mode should warn when using a very small image with placeholder=blur",
"Image Component Default Tests dev mode should work when using flexbox",
"Image Component Default Tests dev mode should work with image with blob src",
"Image Component Default Tests dev mode should work with sizes and automatically use responsive srcset"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Image Component Default Tests dev mode should lazy load with placeholder=blur"
],
"pending": [
"Image Component Default Tests production mode Fill-mode tests should add 100% width and height to fill images",
"Image Component Default Tests production mode Fill-mode tests should add position styles to fill images",
"Image Component Default Tests production mode Fill-mode tests should add position:absolute to fill images",
"Image Component Default Tests production mode Fill-mode tests should include a data-attribute on fill images",
"Image Component Default Tests production mode should apply filter style after image loads",
"Image Component Default Tests production mode should apply style inheritance for img elements but not wrapper elements",
"Image Component Default Tests production mode should be valid HTML",
"Image Component Default Tests production mode should callback native onError even when error before hydration",
"Image Component Default Tests production mode should callback native onError when error occured while loading image",
"Image Component Default Tests production mode should callback native onLoad with sythetic event",
"Image Component Default Tests production mode should callback onLoadingComplete when image is fully loaded",
"Image Component Default Tests production mode should correctly ignore prose styles",
"Image Component Default Tests production mode should correctly rotate image",
"Image Component Default Tests production mode should create images folder in static/media for edge runtime",
"Image Component Default Tests production mode should emit image for next/dynamic with non ssr case",
"Image Component Default Tests production mode should handle the styles prop appropriately",
"Image Component Default Tests production mode should have blurry placeholder when enabled",
"Image Component Default Tests production mode should have data url placeholder when enabled",
"Image Component Default Tests production mode should lazy load with placeholder=blur",
"Image Component Default Tests production mode should load the images",
"Image Component Default Tests production mode should not create an image folder in server/chunks",
"Image Component Default Tests production mode should not pass through user-provided srcset (causing a flash)",
"Image Component Default Tests production mode should preload priority images",
"Image Component Default Tests production mode should remove blurry placeholder after image loads",
"Image Component Default Tests production mode should remove data url placeholder after image loads",
"Image Component Default Tests production mode should render as unoptimized with empty string src prop",
"Image Component Default Tests production mode should render as unoptimized with missing src prop",
"Image Component Default Tests production mode should render correct objectFit when blurDataURL and fill",
"Image Component Default Tests production mode should render correct objectFit when data url placeholder and fill",
"Image Component Default Tests production mode should render no wrappers or sizers",
"Image Component Default Tests production mode should render picture via getImgProps",
"Image Component Default Tests production mode should update the image on src change",
"Image Component Default Tests production mode should warn when legacy prop layout=fill",
"Image Component Default Tests production mode should warn when legacy prop layout=responsive",
"Image Component Default Tests production mode should work when using flexbox",
"Image Component Default Tests production mode should work with image with blob src",
"Image Component Default Tests production mode should work with sizes and automatically use responsive srcset"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-new/default/test/static.test.ts": {
"passed": [
"Static Image Component Tests dev mode Should allow an image with a static src to omit height and width",
"Static Image Component Tests dev mode Should automatically provide an image height and width",
"Static Image Component Tests dev mode should add a data URL placeholder to an image",
"Static Image Component Tests dev mode should add placeholder even when blurDataURL aspect ratio does not match width/height ratio",
"Static Image Component Tests dev mode should add placeholder with blurDataURL and fill",
"Static Image Component Tests dev mode should load direct imported image",
"Static Image Component Tests dev mode should load staticprops imported image",
"Static Image Component Tests dev mode should use height prop to adjust both width and height",
"Static Image Component Tests dev mode should use width and height prop to override import",
"Static Image Component Tests dev mode should use width prop to adjust both width and height"
],
"failed": [
"Static Image Component Tests dev mode should add a blur placeholder a statically imported jpg",
"Static Image Component Tests dev mode should add a blur placeholder a statically imported png",
"Static Image Component Tests dev mode should add a blur placeholder a statically imported png with fill",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Static Image Component Tests dev mode should have <head> containing <meta name=\"viewport\"> followed by <link rel=\"preload\"> for priority image"
],
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Build Error Tests production mode should throw build error when import statement is used with missing file",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Static Image Component Tests production mode Should allow an image with a static src to omit height and width",
"Static Image Component Tests production mode Should automatically provide an image height and width",
"Static Image Component Tests production mode Should use immutable cache-control header even when unoptimized",
"Static Image Component Tests production mode Should use immutable cache-control header for static import",
"Static Image Component Tests production mode should add a blur placeholder a statically imported jpg",
"Static Image Component Tests production mode should add a blur placeholder a statically imported png",
"Static Image Component Tests production mode should add a blur placeholder a statically imported png with fill",
"Static Image Component Tests production mode should add a data URL placeholder to an image",
"Static Image Component Tests production mode should add placeholder even when blurDataURL aspect ratio does not match width/height ratio",
"Static Image Component Tests production mode should add placeholder with blurDataURL and fill",
"Static Image Component Tests production mode should have <head> containing <meta name=\"viewport\"> followed by <link rel=\"preload\"> for priority image",
"Static Image Component Tests production mode should load direct imported image",
"Static Image Component Tests production mode should load staticprops imported image",
"Static Image Component Tests production mode should use height prop to adjust both width and height",
"Static Image Component Tests production mode should use width and height prop to override import",
"Static Image Component Tests production mode should use width prop to adjust both width and height"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-new/export-config/test/index.test.ts": {
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"passed": ["next/image with output export config dev mode should error"],
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/next-image-new/image-from-node-modules/test/index.test.ts": {
"passed": [],
"failed": [
"Image Component from node_modules dev mode should apply image config for node_modules",
"Image Component from node_modules prod mode should apply image config for node_modules"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-new/invalid-image-import/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": ["Missing Import Image Tests dev mode should show error"],
"pending": ["Missing Import Image Tests production mode should show error"],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-new/loader-config-default-loader-with-file/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Loader Config dev mode - component should work with loader prop",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Image Loader Config dev mode - getImgProps should work with loader prop"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
"failed": [
"Image Loader Config dev mode - component should work with loaderFile config, leaving default image optimization enabled",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Image Loader Config dev mode - getImgProps should work with loaderFile config, leaving default image optimization enabled"
],
"pending": [
"Image Loader Config production mode - component should work with loader prop",
"Image Loader Config production mode - component should work with loaderFile config, leaving default image optimization enabled",
"Image Loader Config production mode - getImgProps should work with loader prop",
"Image Loader Config production mode - getImgProps should work with loaderFile config, leaving default image optimization enabled"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/next-image-new/loader-config-edge-runtime/test/index.test.ts": {
"passed": [],
"failed": [
"Image Loader Config with Edge Runtime dev mode should add \"src\" to img1 based on the loader config",
"Image Loader Config with Edge Runtime dev mode should add \"src\" to img2 based on the loader prop",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Loader Config with Edge Runtime dev mode should add \"srcset\" to img1 based on the loader config",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Image Loader Config with Edge Runtime dev mode should add \"srcset\" to img2 based on the loader prop"
],
"pending": [
"Image Loader Config with Edge Runtime production mode should add \"src\" to img1 based on the loader config",
"Image Loader Config with Edge Runtime production mode should add \"src\" to img2 based on the loader prop",
"Image Loader Config with Edge Runtime production mode should add \"srcset\" to img1 based on the loader config",
"Image Loader Config with Edge Runtime production mode should add \"srcset\" to img2 based on the loader prop"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-new/loader-config/test/index.test.ts": {
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Image Loader Config new dev mode - component should work with loader prop",
"Image Loader Config new dev mode - component should work with loaderFile config",
"Image Loader Config new dev mode - getImgProps should work with loader prop",
"Image Loader Config new dev mode - getImgProps should work with loaderFile config"
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
],
"pending": [
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Image Loader Config new production mode - component should work with loader prop",
"Image Loader Config new production mode - component should work with loaderFile config",
"Image Loader Config new production mode - getImgProps should work with loader prop",
"Image Loader Config new production mode - getImgProps should work with loaderFile config"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-new/middleware/test/index.test.ts": {
"passed": ["Image with middleware in edge func dev mode should not error"],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-new/react-virtualized/test/index.test.ts": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"react-virtualized wrapping next/image production mode should not cancel requests for images"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/next-image-new/svgo-webpack/test/index.test.ts": {
"passed": [],
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"svgo-webpack with Image Component development mode should print error when invalid Image usage",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"svgo-webpack with Image Component production mode should not fail to build invalid usage of the Image component"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-new/trailing-slash/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Component Trailing Slash Tests dev mode should include trailing slash when trailingSlash is set on config file during next dev"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
"pending": [
"Image Component Trailing Slash Tests production mode should include trailing slash when trailingSlash is set on config file during next start"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-new/typescript/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"TypeScript Image Component development mode should have image types when enabled",
"TypeScript Image Component development mode should print error when invalid Image usage",
"TypeScript Image Component development mode should render the valid Image usage and not print error",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"TypeScript Image Component should remove global image types when disabled (dev)"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"TypeScript Image Component production mode should fail to build invalid usage of the Image component",
"TypeScript Image Component production mode should remove global image types when disabled"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/next-image-new/unicode/test/index.test.ts": {
"passed": [],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
"pending": [],
"flakey": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Component Unicode Image URL dev mode should load external image with space",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Image Component Unicode Image URL dev mode should load external unicode image",
"Image Component Unicode Image URL dev mode should load internal image with space",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Image Component Unicode Image URL dev mode should load internal unicode image",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"Image Component Unicode Image URL dev mode should load static unicode image",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Image Component Unicode Image URL production mode should load external image with space",
"Image Component Unicode Image URL production mode should load external unicode image",
"Image Component Unicode Image URL production mode should load internal image with space",
"Image Component Unicode Image URL production mode should load internal unicode image",
"Image Component Unicode Image URL production mode should load static unicode image"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/next-image-new/unoptimized/test/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Unoptimized Image Tests dev mode - component should not optimize any image",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Unoptimized Image Tests dev mode - getImgProps should not optimize any image"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"Unoptimized Image Tests production mode - component should not optimize any image",
"Unoptimized Image Tests production mode - getImgProps should not optimize any image"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/no-duplicate-compile-error/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"no duplicate compile error output should not show compile error on page refresh"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/no-op-export/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"no-op export production mode should not error for all server-side pages build",
"no-op export production mode should not error for empty exportPathMap"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/no-override-next-props/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic require should show error when a Next prop is returned in _app.getInitialProps"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/no-page-props/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Error no pageProps dev mode should load 404 page correctly",
"Error no pageProps dev mode should load auto-export page correctly",
"Error no pageProps dev mode should load getServerSideProps page correctly",
"Error no pageProps dev mode should load getStaticProps page correctly",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Error no pageProps dev mode should navigate between pages correctly"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Error no pageProps production mode should load 404 page correctly",
"Error no pageProps production mode should load auto-export page correctly",
"Error no pageProps production mode should load getServerSideProps page correctly",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Error no pageProps production mode should load getStaticProps page correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Error no pageProps production mode should navigate between pages correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/node-fetch-keep-alive/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"node-fetch-keep-alive dev should send keep-alive for getServerSideProps",
"node-fetch-keep-alive dev should send keep-alive for getStaticPaths",
"node-fetch-keep-alive dev should send keep-alive for getStaticProps",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"node-fetch-keep-alive dev should send keep-alive for json API"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"node-fetch-keep-alive production mode should send keep-alive for getServerSideProps",
"node-fetch-keep-alive production mode should send keep-alive for getStaticPaths",
"node-fetch-keep-alive production mode should send keep-alive for getStaticProps",
"node-fetch-keep-alive production mode should send keep-alive for json API"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/non-next-dist-exclude/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Non-Next externalization production mode Externalized non-Next dist-using package"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/non-standard-node-env-warning/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Non-Standard NODE_ENV should not show the warning with NODE_ENV set to valid value",
"Non-Standard NODE_ENV should not show the warning with NODE_ENV set to valid value (custom server)",
"Non-Standard NODE_ENV should not show the warning with no NODE_ENV set",
"Non-Standard NODE_ENV should show the warning with NODE_ENV set to invalid value",
"Non-Standard NODE_ENV should show the warning with NODE_ENV set to invalid value (custom server)",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Non-Standard NODE_ENV should show the warning with NODE_ENV set to production with next dev"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Non-Standard NODE_ENV production mode should show the warning with NODE_ENV set to development with next build",
"Non-Standard NODE_ENV production mode should show the warning with NODE_ENV set to development with next start",
"Non-Standard NODE_ENV production mode should still DCE NODE_ENV specific code"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/not-found-revalidate/test/index.test.js": {
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"passed": [],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"SSG notFound revalidate production mode should revalidate after notFound is returned for fallback: blocking",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"SSG notFound revalidate production mode should revalidate after notFound is returned for fallback: true",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"SSG notFound revalidate production mode should revalidate page when notFund returned during build"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/nullish-config/test/index.test.js": {
"passed": [
"Nullish configs in next.config.js dev mode should ignore configs set to `null` in next.config.js",
"Nullish configs in next.config.js dev mode should ignore configs set to `undefined` in next.config.js"
],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Nullish configs in next.config.js production mode should ignore configs set to `null` in next.config.js",
"Nullish configs in next.config.js production mode should ignore configs set to `undefined` in next.config.js"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/numeric-sep/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Numeric Separator Support production mode should successfully build for a JavaScript file"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/ondemand/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"On Demand Entries should compile pages for JSON page requests",
"On Demand Entries should compile pages for SSR",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"On Demand Entries should dispose inactive pages",
"On Demand Entries should navigate to pages with dynamic imports",
"On Demand Entries should pass"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/optional-chaining-nullish-coalescing/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Optional chaining and nullish coalescing support dev mode should support nullish coalescing",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Optional chaining and nullish coalescing support dev mode should support optional chaining"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"Optional chaining and nullish coalescing support production mode should support nullish coalescing",
"Optional chaining and nullish coalescing support production mode should support optional chaining"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/page-config/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"Page Config production mode builds without error when export const config is used outside page",
"Page Config production mode shows error when page config has invalid properties",
"Page Config production mode shows error when page config has invalid property value",
"Page Config production mode shows error when page config has spread properties",
"Page Config production mode shows error when page config is export from",
"Page Config production mode shows error when page config is imported and exported",
"Page Config production mode shows valid error when page config has no init",
"Page Config production mode shows valid error when page config is a string"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/page-extensions/test/index.test.js": {
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"passed": [],
"failed": [],
"pending": [
"Page Extensions production mode should not throw if .d.ts file inside the pages folder",
"Page Extensions production mode should throw if pageExtensions has invalid extensions",
"Page Extensions production mode should throw if pageExtensions is an empty array",
"Page Extensions production mode should use the default pageExtensions if set to undefined"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/plugin-mdx-rs/test/index.test.js": {
"passed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"MDX-rs Configuration MDX-rs Plugin support should render an MDX page correctly",
"MDX-rs Configuration MDX-rs Plugin support should render an MDX page with component correctly",
"MDX-rs Configuration MDX-rs Plugin support should render an MDX page with globally provided components (from `mdx-components.js`) correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/polyfilling-minimal/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Polyfilling (minimal) production mode should compile successfully"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/polyfills/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"Polyfills production mode should alias fetch",
"Polyfills production mode should allow using process.env when there is an element with `id` of `process`",
"Polyfills production mode should contain generated page count in output"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/port-env-var/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"PORT environment variable dev mode should serve on the configured port"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"PORT environment variable production mode should serve on the configured port"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/preload-viewport/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"Prefetching Links in viewport production mode should correctly omit pre-generated dynamic pages from SSG manifest",
"Prefetching Links in viewport production mode should de-dupe inflight SSG requests",
"Prefetching Links in viewport production mode should handle timed out prefetch correctly",
"Prefetching Links in viewport production mode should inject a <script> tag when onMouseEnter (even with invalid ref)",
"Prefetching Links in viewport production mode should inject script on hover with prefetching disabled",
"Prefetching Links in viewport production mode should inject script on hover with prefetching disabled and fetch data",
"Prefetching Links in viewport production mode should not duplicate prefetches",
"Prefetching Links in viewport production mode should not have unhandledRejection when failing to prefetch on link",
"Prefetching Links in viewport production mode should not prefetch already loaded scripts",
"Prefetching Links in viewport production mode should not prefetch when prefetch is explicitly set to false",
"Prefetching Links in viewport production mode should not prefetch with bot UA",
"Prefetching Links in viewport production mode should not re-prefetch for an already prefetched page",
"Prefetching Links in viewport production mode should prefetch data files",
"Prefetching Links in viewport production mode should prefetch data files when mismatched",
"Prefetching Links in viewport production mode should prefetch rewritten href with link in viewport onload",
"Prefetching Links in viewport production mode should prefetch with a different asPath for a prefetched page",
"Prefetching Links in viewport production mode should prefetch with link in viewport and inject script on hover",
"Prefetching Links in viewport production mode should prefetch with link in viewport on scroll",
"Prefetching Links in viewport production mode should prefetch with link in viewport onload",
"Prefetching Links in viewport production mode should prefetch with link in viewport when href changes",
"Prefetching Links in viewport production mode should prefetch with non-bot UA"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"test/integration/prerender-export/test/index.test.js": {
"passed": [],
"failed": [],
"pending": [
"SSG Prerender export production mode export mode should copy prerender files and honor exportTrailingSlash",
"SSG Prerender export production mode export mode should navigate between pages successfully"
],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/prerender-fallback-encoding/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Fallback path encoding dev mode should navigate client-side correctly with interpolating",
"Fallback path encoding dev mode should navigate client-side correctly with string href",
"Fallback path encoding dev mode should render correctly in the browser for prerender paths",
"Fallback path encoding dev mode should respond with the prerendered data correctly",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Fallback path encoding dev mode should respond with the prerendered pages correctly"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Fallback path encoding production mode should handle non-prerendered paths correctly",
"Fallback path encoding production mode should navigate client-side correctly with interpolating",
"Fallback path encoding production mode should navigate client-side correctly with string href",
"Fallback path encoding production mode should output paths correctly",
"Fallback path encoding production mode should render correctly in the browser for prerender paths",
"Fallback path encoding production mode should respond with the prerendered data correctly",
"Fallback path encoding production mode should respond with the prerendered pages correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/prerender-invalid-catchall-params/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Invalid Prerender Catchall Params production mode should fail the build"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/prerender-invalid-paths/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Legacy Prerender production mode handles old getStaticParams should fail the build"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/prerender-no-revalidate/test/index.test.js": {
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"passed": [],
"failed": [],
"pending": [
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"SSG Prerender No Revalidate production mode [/] should not revalidate /_next/data when set to false",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"SSG Prerender No Revalidate production mode [/] should not revalidate when set to false",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"SSG Prerender No Revalidate production mode [/named] should not revalidate /_next/data when set to false",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"SSG Prerender No Revalidate production mode [/named] should not revalidate when set to false",
"SSG Prerender No Revalidate production mode [/nested/named] should not revalidate /_next/data when set to false",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"SSG Prerender No Revalidate production mode [/nested/named] should not revalidate when set to false",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"SSG Prerender No Revalidate production mode [/nested] should not revalidate /_next/data when set to false",
"SSG Prerender No Revalidate production mode [/nested] should not revalidate when set to false"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/prerender-preview/test/index.test.js": {
"passed": [
"Prerender Preview Mode Development Mode should enable preview mode",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Prerender Preview Mode Development Mode should fetch live static props with preview active",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Prerender Preview Mode Development Mode should fetch prerendered data",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Prerender Preview Mode Development Mode should fetch preview data on CST",
"Prerender Preview Mode Development Mode should fetch preview data on SSR",
"Prerender Preview Mode Development Mode should return cookies to be expired after dev server reboot",
"Prerender Preview Mode Development Mode should start development application",
"Prerender Preview Mode Development Mode should start the client-side browser"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
"pending": [
"Prerender Preview Mode production mode should compile successfully",
"Prerender Preview Mode production mode should enable preview mode",
"Prerender Preview Mode production mode should expire cookies with a maxAge",
"Prerender Preview Mode production mode should not return fallback page on preview request",
"Prerender Preview Mode production mode should pass the preview data to API routes",
"Prerender Preview Mode production mode should pass undefined to API routes when not in preview",
"Prerender Preview Mode production mode should return cookies to be expired on reset request",
"Prerender Preview Mode production mode should return cookies to be expired on reset request with path specified",
"Prerender Preview Mode production mode should return correct caching headers for data preview request",
"Prerender Preview Mode production mode should return prerendered page on first request",
"Prerender Preview Mode production mode should return prerendered page on second request",
"Prerender Preview Mode production mode should set custom path cookies",
"Prerender Preview Mode production mode should start production application",
"Prerender Preview Mode production mode should throw error when setting too large of preview data"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/prerender-revalidate/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"failed": [],
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"SSG Prerender Revalidate [regression] production mode and incremental cache size exceeded production mode [/] should regenerate /_next/data when revalidate time exceeded",
"SSG Prerender Revalidate [regression] production mode and incremental cache size exceeded production mode [/] should regenerate page when revalidate time exceeded",
"SSG Prerender Revalidate [regression] production mode and incremental cache size exceeded production mode [/named] should regenerate /_next/data when revalidate time exceeded",
"SSG Prerender Revalidate [regression] production mode and incremental cache size exceeded production mode [/named] should regenerate page when revalidate time exceeded",
"SSG Prerender Revalidate [regression] production mode and incremental cache size exceeded production mode [/nested/named] should regenerate /_next/data when revalidate time exceeded",
"SSG Prerender Revalidate [regression] production mode and incremental cache size exceeded production mode [/nested/named] should regenerate page when revalidate time exceeded",
"SSG Prerender Revalidate [regression] production mode and incremental cache size exceeded production mode [/nested] should regenerate /_next/data when revalidate time exceeded",
"SSG Prerender Revalidate [regression] production mode and incremental cache size exceeded production mode [/nested] should regenerate page when revalidate time exceeded",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"SSG Prerender Revalidate production mode [/] should regenerate /_next/data when revalidate time exceeded",
"SSG Prerender Revalidate production mode [/] should regenerate page when revalidate time exceeded",
"SSG Prerender Revalidate production mode [/named] should regenerate /_next/data when revalidate time exceeded",
"SSG Prerender Revalidate production mode [/named] should regenerate page when revalidate time exceeded",
"SSG Prerender Revalidate production mode [/nested/named] should regenerate /_next/data when revalidate time exceeded",
"SSG Prerender Revalidate production mode [/nested/named] should regenerate page when revalidate time exceeded",
"SSG Prerender Revalidate production mode [/nested] should regenerate /_next/data when revalidate time exceeded",
"SSG Prerender Revalidate production mode [/nested] should regenerate page when revalidate time exceeded",
"SSG Prerender Revalidate production mode should return cache-control header on 304 status"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/prerender/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"SSG Prerender dev mode getStaticPaths should not cache getStaticPaths errors",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"SSG Prerender dev mode getStaticPaths should work with firebase import and getStaticPaths"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/preview-fallback/test/index.test.js": {
"passed": [
"Preview mode with fallback pages dev Mode should get preview cookie correctly",
"Preview mode with fallback pages dev Mode should not write preview dynamic SSG page to cache no fallback",
"Preview mode with fallback pages dev Mode should not write preview dynamic non-prerendered SSG page to cache with fallback",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Preview mode with fallback pages dev Mode should not write preview dynamic prerendered SSG page to cache no fallback",
"Preview mode with fallback pages dev Mode should not write preview dynamic prerendered SSG page to cache with fallback",
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Preview mode with fallback pages dev Mode should not write preview index SSG page to cache"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"Preview mode with fallback pages production mode should get preview cookie correctly",
"Preview mode with fallback pages production mode should not write preview dynamic SSG page to cache no fallback",
"Preview mode with fallback pages production mode should not write preview dynamic non-prerendered SSG page to cache with fallback",
"Preview mode with fallback pages production mode should not write preview dynamic prerendered SSG page to cache no fallback",
"Preview mode with fallback pages production mode should not write preview dynamic prerendered SSG page to cache with fallback",
"Preview mode with fallback pages production mode should not write preview index SSG page to cache"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/production-browser-sourcemaps/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"Production browser sourcemaps production mode Server support correctly generated the source map",
"Production browser sourcemaps production mode Server support includes sourcemaps for all browser files"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/production-build-dir/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Production Custom Build Directory production mode With basic usage should render the page"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/production-config/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"Production Config Usage production mode env should allow __ within env key",
"Production Config Usage production mode env should fail with NEXT_RUNTIME in env key",
"Production Config Usage production mode env should fail with NODE_ in env key",
"Production Config Usage production mode env should fail with leading __ in env key",
"Production Config Usage production mode with generateBuildId should add the custom buildid"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/production-nav/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Production Usage production mode should navigate forward and back correctly"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/production-start-no-build/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Production Usage without production build should show error when there is no production build"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"test/integration/query-with-encoding/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
"failed": [],
"pending": [
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Query String with Encoding production mode new line should have correct query on Router#push",
"Query String with Encoding production mode new line should have correct query on SSR",
"Query String with Encoding production mode new line should have correct query on complex client-side <Link>",
"Query String with Encoding production mode new line should have correct query on simple client-side <Link>",
"Query String with Encoding production mode percent should have correct query on Router#push",
"Query String with Encoding production mode percent should have correct query on SSR",
"Query String with Encoding production mode percent should have correct query on complex client-side <Link>",
"Query String with Encoding production mode percent should have correct query on simple client-side <Link>",
"Query String with Encoding production mode plus should have correct query on Router#push",
"Query String with Encoding production mode plus should have correct query on SSR",
"Query String with Encoding production mode plus should have correct query on complex client-side <Link>",
"Query String with Encoding production mode plus should have correct query on simple client-side <Link>",
"Query String with Encoding production mode trailing space should have correct query on Router#push",
"Query String with Encoding production mode trailing space should have correct query on SSR",
"Query String with Encoding production mode trailing space should have correct query on complex client-side <Link>",
"Query String with Encoding production mode trailing space should have correct query on simple client-side <Link>"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/re-export-all-exports-from-page-disallowed/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Re-export all exports from page is disallowed production mode builds without error when no `export * from \"...\"` is used in pages",
"Re-export all exports from page is disallowed production mode shows error when a page re-export all exports"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/react-18/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Basics default setting with react 18 dev hydrates correctly for normal page",
"Basics default setting with react 18 dev no warnings for image related link props",
update test manifest (#57105) update test manifest from daily test run Closes WEB-1809
2023-10-22 21:00:00 +02:00
"Basics default setting with react 18 dev should contain dynamicIds in next data for dynamic imports",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Basics default setting with react 18 dev should only render once in SSR",
"Basics default setting with react 18 dev useId() values should match on hydration",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"Concurrent mode in the experimental-edge runtime dev <RouteAnnouncer /> should not have the initial route announced",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Concurrent mode in the experimental-edge runtime dev flushes styled-jsx styles as the page renders",
"Concurrent mode in the experimental-edge runtime dev should not have invalid config warning",
"Concurrent mode in the nodejs runtime dev <RouteAnnouncer /> should not have the initial route announced",
"Concurrent mode in the nodejs runtime dev flushes styled-jsx styles as the page renders",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Concurrent mode in the nodejs runtime dev should not have invalid config warning"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Basics production mode default setting with react 18 prod hydrates correctly for normal page",
"Basics production mode default setting with react 18 prod no warnings for image related link props",
"Basics production mode default setting with react 18 prod should contain dynamicIds in next data for dynamic imports",
"Basics production mode default setting with react 18 prod should only render once in SSR",
"Basics production mode default setting with react 18 prod useId() values should match on hydration",
"production mode Concurrent mode in the experimental-edge runtime prod <RouteAnnouncer /> should not have the initial route announced",
"production mode Concurrent mode in the experimental-edge runtime prod flushes styled-jsx styles as the page renders",
"production mode Concurrent mode in the experimental-edge runtime prod should not have invalid config warning",
"production mode Concurrent mode in the nodejs runtime prod <RouteAnnouncer /> should not have the initial route announced",
"production mode Concurrent mode in the nodejs runtime prod flushes styled-jsx styles as the page renders",
"production mode Concurrent mode in the nodejs runtime prod should not have invalid config warning"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/react-profiling-mode/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"React Profiling Mode production mode with config enabled should have used the react-dom profiling bundle for client component",
"React Profiling Mode production mode with config enabled should have used the react-dom profiling bundle for pages",
"React Profiling Mode production mode with config enabled should have used the react-dom profiling bundle for server component",
"React Profiling Mode production mode without config enabled should not have used the react-dom profiling bundle"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/react-streaming/test/index.test.js": {
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"streaming dev dev should not stream to crawlers or google pagerender bot",
Revert "fix turbopack invalidations (#57362)" (#57480) ### Why? breaks hmr and causes some duplicate react instances (it was also supposed to fix some of those, seems neither version is correct) Closes WEB-1882
2023-10-26 08:14:11 +02:00
"streaming dev dev should render 500 error correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"streaming dev dev should render fallback if error raised from suspense during streaming",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"streaming dev dev should support streaming for fizz response"
],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"production mode streaming prod prod should not stream to crawlers or google pagerender bot",
"production mode streaming prod prod should render 500 error correctly",
"production mode streaming prod prod should render fallback if error raised from suspense during streaming",
"production mode streaming prod prod should support streaming for fizz response"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
Revert "fix turbopack invalidations (#57362)" (#57480) ### Why? breaks hmr and causes some duplicate react instances (it was also supposed to fix some of those, seems neither version is correct) Closes WEB-1882
2023-10-26 08:14:11 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/read-only-source-hmr/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Read-only source HMR should detect a new page",
"Read-only source HMR should detect changes to a page",
"Read-only source HMR should handle page deletion and subsequent recreation"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/relay-analytics-disabled/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"Analytics relayer (disabled) production mode Does not include the code",
"Analytics relayer (disabled) production mode Does not relay any data"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/relay-analytics/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Analytics relayer with exported method production mode Relays the data to user code",
"Analytics relayer with exported method production mode reports INP metric",
"Analytics relayer with exported method production mode reports attribution"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/relay-graphql-swc-multi-project/test/index.test.js": {
"passed": [],
"failed": [
"Relay Compiler Transform - Multi Project Config dev mode project-a should resolve index page correctly",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Relay Compiler Transform - Multi Project Config dev mode project-b should resolve index page correctly"
],
"pending": [
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Relay Compiler Transform - Multi Project Config production mode project-a should resolve index page correctly",
"Relay Compiler Transform - Multi Project Config production mode project-b should resolve index page correctly"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/relay-graphql-swc-single-project/test/index.test.js": {
"passed": [
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Relay Compiler Transform - Single Project Config dev mode should resolve index page correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"Relay Compiler Transform - Single Project Config production mode should resolve index page correctly"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/render-error-on-module-error/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": ["Module Init Error production mode should render error page"],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/render-error-on-top-level-error/with-get-initial-props/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Top Level Error production mode should render error page with getInitialProps"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/render-error-on-top-level-error/without-get-initial-props/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": ["Top Level Error production mode should render error page"],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/repeated-slashes/test/index.test.js": {
"passed": [
"404 handling custom _error next dev should handle backslashes correctly",
"404 handling custom _error next dev should handle double slashes correctly",
"404 handling custom _error next dev should handle double slashes correctly with encoded",
"404 handling custom _error next dev should handle double slashes correctly with encoded and hash",
"404 handling custom _error next dev should handle double slashes correctly with encoded and query",
"404 handling custom _error next dev should handle double slashes correctly with hash",
"404 handling custom _error next dev should handle double slashes correctly with query",
"404 handling custom _error next dev should handle mixed backslashes/forward slashes correctly",
"404 handling custom _error next dev should handle slashes in next/link correctly",
"404 handling custom _error next dev should handle slashes in router push correctly",
"404 handling custom _error next dev should have no error from encoded slashes in router push",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"404 handling custom _error next dev should normalize repeated slashes in redirects correctly"
],
"failed": [],
"pending": [
"404 handling custom _error production mode next export should handle backslashes correctly",
"404 handling custom _error production mode next export should handle double slashes correctly",
"404 handling custom _error production mode next export should handle double slashes correctly with encoded",
"404 handling custom _error production mode next export should handle double slashes correctly with encoded and hash",
"404 handling custom _error production mode next export should handle double slashes correctly with encoded and query",
"404 handling custom _error production mode next export should handle double slashes correctly with hash",
"404 handling custom _error production mode next export should handle double slashes correctly with query",
"404 handling custom _error production mode next export should handle mixed backslashes/forward slashes correctly",
"404 handling custom _error production mode next export should handle slashes in next/link correctly",
"404 handling custom _error production mode next export should handle slashes in router push correctly",
"404 handling custom _error production mode next export should have no error from encoded slashes in router push",
"404 handling custom _error production mode next start should handle backslashes correctly",
"404 handling custom _error production mode next start should handle double slashes correctly",
"404 handling custom _error production mode next start should handle double slashes correctly with encoded",
"404 handling custom _error production mode next start should handle double slashes correctly with encoded and hash",
"404 handling custom _error production mode next start should handle double slashes correctly with encoded and query",
"404 handling custom _error production mode next start should handle double slashes correctly with hash",
"404 handling custom _error production mode next start should handle double slashes correctly with query",
"404 handling custom _error production mode next start should handle mixed backslashes/forward slashes correctly",
"404 handling custom _error production mode next start should handle slashes in next/link correctly",
"404 handling custom _error production mode next start should handle slashes in router push correctly",
"404 handling custom _error production mode next start should have no error from encoded slashes in router push",
"404 handling custom _error production mode next start should normalize repeated slashes in redirects correctly",
"404 handling pages/404 production mode next dev should handle backslashes correctly",
"404 handling pages/404 production mode next dev should handle double slashes correctly",
"404 handling pages/404 production mode next dev should handle double slashes correctly with encoded",
"404 handling pages/404 production mode next dev should handle double slashes correctly with encoded and hash",
"404 handling pages/404 production mode next dev should handle double slashes correctly with encoded and query",
"404 handling pages/404 production mode next dev should handle double slashes correctly with hash",
"404 handling pages/404 production mode next dev should handle double slashes correctly with query",
"404 handling pages/404 production mode next dev should handle mixed backslashes/forward slashes correctly",
"404 handling pages/404 production mode next dev should handle slashes in next/link correctly",
"404 handling pages/404 production mode next dev should handle slashes in router push correctly",
"404 handling pages/404 production mode next dev should have no error from encoded slashes in router push",
"404 handling pages/404 production mode next dev should normalize repeated slashes in redirects correctly",
"404 handling pages/404 production mode production mode next export should handle backslashes correctly",
"404 handling pages/404 production mode production mode next export should handle double slashes correctly",
"404 handling pages/404 production mode production mode next export should handle double slashes correctly with encoded",
"404 handling pages/404 production mode production mode next export should handle double slashes correctly with encoded and hash",
"404 handling pages/404 production mode production mode next export should handle double slashes correctly with encoded and query",
"404 handling pages/404 production mode production mode next export should handle double slashes correctly with hash",
"404 handling pages/404 production mode production mode next export should handle double slashes correctly with query",
"404 handling pages/404 production mode production mode next export should handle mixed backslashes/forward slashes correctly",
"404 handling pages/404 production mode production mode next export should handle slashes in next/link correctly",
"404 handling pages/404 production mode production mode next export should handle slashes in router push correctly",
"404 handling pages/404 production mode production mode next export should have no error from encoded slashes in router push",
"404 handling pages/404 production mode production mode next start should handle backslashes correctly",
"404 handling pages/404 production mode production mode next start should handle double slashes correctly",
"404 handling pages/404 production mode production mode next start should handle double slashes correctly with encoded",
"404 handling pages/404 production mode production mode next start should handle double slashes correctly with encoded and hash",
"404 handling pages/404 production mode production mode next start should handle double slashes correctly with encoded and query",
"404 handling pages/404 production mode production mode next start should handle double slashes correctly with hash",
"404 handling pages/404 production mode production mode next start should handle double slashes correctly with query",
"404 handling pages/404 production mode production mode next start should handle mixed backslashes/forward slashes correctly",
"404 handling pages/404 production mode production mode next start should handle slashes in next/link correctly",
"404 handling pages/404 production mode production mode next start should handle slashes in router push correctly",
"404 handling pages/404 production mode production mode next start should have no error from encoded slashes in router push",
"404 handling pages/404 production mode production mode next start should normalize repeated slashes in redirects correctly"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/required-server-files-ssr-404/test/index.test.js": {
"passed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Required Server Files production mode should bubble error correctly for gip page",
"Required Server Files production mode should bubble error correctly for gsp page",
"Required Server Files production mode should bubble error correctly for gssp page",
"Required Server Files production mode should handle 404s properly",
"Required Server Files production mode should match the index page correctly",
"Required Server Files production mode should match the root dynamic page correctly",
"Required Server Files production mode should normalize catch-all rewrite query values correctly",
"Required Server Files production mode should normalize optional values correctly for API page",
"Required Server Files production mode should normalize optional values correctly for SSG page",
"Required Server Files production mode should normalize optional values correctly for SSP page",
"Required Server Files production mode should not apply trailingSlash redirect",
"Required Server Files production mode should output required-server-files manifest correctly",
"Required Server Files production mode should render SSR page correctly",
"Required Server Files production mode should render SSR page correctly with x-matched-path",
"Required Server Files production mode should render dynamic SSR page correctly",
"Required Server Files production mode should render dynamic SSR page correctly with x-matched-path",
"Required Server Files production mode should render fallback optional catch-all route correctly with x-matched-path and routes-matches",
"Required Server Files production mode should render fallback page correctly",
"Required Server Files production mode should render fallback page correctly with x-matched-path and routes-matches",
"Required Server Files production mode should return data correctly with x-matched-path",
"Required Server Files production mode should return data correctly with x-matched-path for optional catch-all route"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"runtimeError": false
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
},
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"test/integration/revalidate-as-path/test/index.test.js": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"Revalidate asPath Normalizing production mode should render with correct asPath with / requested",
"Revalidate asPath Normalizing production mode should render with correct asPath with /_next/data /another/index requested",
"Revalidate asPath Normalizing production mode should render with correct asPath with /_next/data /index requested",
"Revalidate asPath Normalizing production mode should render with correct asPath with /another/index requested"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/rewrite-with-browser-history/test/index.test.js": {
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"passed": [
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"rewrites persist with browser history actions dev mode back-button should go back to rewritten path successfully"
],
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"rewrites persist with browser history actions production mode back-button should go back to rewritten path successfully"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/rewrites-client-resolving/test/index.test.js": {
"passed": [
"Client-side rewrites resolving dev mode should break rewrites chain after matching /category",
"Client-side rewrites resolving dev mode should break rewrites chain when dynamic catch-all route matches",
"Client-side rewrites resolving dev mode should break rewrites chain when dynamic catch-all route multi-level matches",
"Client-side rewrites resolving dev mode should break rewrites chain when dynamic route matches",
"Client-side rewrites resolving dev mode should break rewrites chain when normal page matches"
],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Client-side rewrites resolving production mode should break rewrites chain after matching /category",
"Client-side rewrites resolving production mode should break rewrites chain when dynamic catch-all route matches",
"Client-side rewrites resolving production mode should break rewrites chain when dynamic catch-all route multi-level matches",
"Client-side rewrites resolving production mode should break rewrites chain when dynamic route matches",
"Client-side rewrites resolving production mode should break rewrites chain when normal page matches"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
},
"test/integration/rewrites-destination-query-array/test/index.test.js": {
"passed": [
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"rewrites destination query dev mode should contain all values passed in param as array"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"rewrites destination query production mode should contain all values passed in param as array"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/rewrites-has-condition/test/index.test.js": {
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"passed": [
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"rewrites has condition dev mode should navigate to a has rewrite without error",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"rewrites has condition dev mode should navigate to a simple rewrite without error"
],
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"rewrites has condition production mode should navigate to a has rewrite without error",
"rewrites has condition production mode should navigate to a simple rewrite without error"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/rewrites-manual-href-as/test/index.test.js": {
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"rewrites manual href/as dev mode should allow manual href/as on dynamic page",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"rewrites manual href/as dev mode should allow manual href/as on index page"
],
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"rewrites manual href/as production mode should allow manual href/as on dynamic page",
"rewrites manual href/as production mode should allow manual href/as on index page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/root-optional-revalidate/test/index.test.js": {
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"passed": [],
"failed": [],
"pending": [
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Root Optional Catch-all Revalidate production mode should render / correctly",
"Root Optional Catch-all Revalidate production mode should render /a correctly",
"Root Optional Catch-all Revalidate production mode should render /hello/world correctly"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/route-index/test/index.test.js": {
"passed": [
"Route index handling dev mode should handle / correctly",
"Route index handling dev mode should handle /index correctly",
"Route index handling dev mode should handle /index/?bar%60%3C%25%22%27%7B%24%2A%25%5C correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Route index handling dev mode should handle /index/index correctly",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Route index handling dev mode should handle /index?file%3A%5C correctly"
],
"failed": [],
"pending": [
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Route index handling production mode should handle / correctly",
"Route index handling production mode should handle /index correctly",
"Route index handling production mode should handle /index/?bar%60%3C%25%22%27%7B%24%2A%25%5C correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Route index handling production mode should handle /index/index correctly",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Route index handling production mode should handle /index?file%3A%5C correctly"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
"test/integration/route-indexes/test/index.test.js": {
"passed": [
"Route indexes handling dev mode should handle / correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Route indexes handling dev mode should handle /api/sub correctly",
"Route indexes handling dev mode should handle /api/sub/another correctly",
"Route indexes handling dev mode should handle /api/sub/another/index correctly",
"Route indexes handling dev mode should handle /api/sub/index correctly",
"Route indexes handling dev mode should handle /api/sub/index/index correctly",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Route indexes handling dev mode should handle /index correctly",
"Route indexes handling dev mode should handle /index/index correctly",
"Route indexes handling dev mode should handle /nested-index correctly",
"Route indexes handling dev mode should handle /nested-index/index correctly",
"Route indexes handling dev mode should handle /nested-index/index/index correctly",
"Route indexes handling dev mode should handle /sub correctly",
"Route indexes handling dev mode should handle /sub/another correctly",
"Route indexes handling dev mode should handle /sub/another/index correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Route indexes handling dev mode should handle /sub/index correctly",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Route indexes handling dev mode should handle /sub/index/index correctly"
],
"failed": [],
"pending": [
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Route indexes handling production mode should handle / correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Route indexes handling production mode should handle /api/sub correctly",
"Route indexes handling production mode should handle /api/sub/another correctly",
"Route indexes handling production mode should handle /api/sub/another/index correctly",
"Route indexes handling production mode should handle /api/sub/index correctly",
"Route indexes handling production mode should handle /api/sub/index/index correctly",
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"Route indexes handling production mode should handle /index correctly",
"Route indexes handling production mode should handle /index/index correctly",
"Route indexes handling production mode should handle /nested-index correctly",
"Route indexes handling production mode should handle /nested-index/index correctly",
"Route indexes handling production mode should handle /nested-index/index/index correctly",
"Route indexes handling production mode should handle /sub correctly",
"Route indexes handling production mode should handle /sub/another correctly",
"Route indexes handling production mode should handle /sub/another/index correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Route indexes handling production mode should handle /sub/index correctly",
"Route indexes handling production mode should handle /sub/index/index correctly"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/route-load-cancel-css/test/index.test.js": {
"passed": [],
"failed": [
"route cancel via CSS should cancel slow page loads on re-navigation"
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/route-load-cancel/test/index.test.js": {
"passed": [
"next/dynamic dev mode should cancel slow page loads on re-navigation"
],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"next/dynamic production mode should cancel slow page loads on re-navigation"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/router-hash-navigation/test/index.test.js": {
"passed": [
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"router.isReady dev mode scrolls to top when href=\"/\" and url already contains a hash"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"router.isReady production mode scrolls to top when href=\"/\" and url already contains a hash"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/router-is-ready-app-gip/test/index.test.js": {
"passed": [
"router.isReady with appGip dev mode isReady should be true after query update for getStaticProps page with query",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"router.isReady with appGip dev mode isReady should be true immediately for getStaticProps page without query",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"router.isReady with appGip dev mode isReady should be true immediately for pages without getStaticProps",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"router.isReady with appGip dev mode isReady should be true immediately for pages without getStaticProps, with query"
],
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"router.isReady with appGip production mode isReady should be true after query update for getStaticProps page with query",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"router.isReady with appGip production mode isReady should be true immediately for getStaticProps page without query",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"router.isReady with appGip production mode isReady should be true immediately for pages without getStaticProps",
"router.isReady with appGip production mode isReady should be true immediately for pages without getStaticProps, with query"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/router-is-ready/test/index.test.js": {
"passed": [
"router.isReady dev mode isReady should be true after query update for auto-export page with query",
"router.isReady dev mode isReady should be true after query update for dynamic auto-export page with query",
"router.isReady dev mode isReady should be true after query update for dynamic auto-export page without query",
"router.isReady dev mode isReady should be true after query update for getStaticProps page with query",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"router.isReady dev mode isReady should be true immediately for auto-export page without query",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"router.isReady dev mode isReady should be true immediately for getInitialProps page",
"router.isReady dev mode isReady should be true immediately for getInitialProps page with query",
"router.isReady dev mode isReady should be true immediately for getServerSideProps page",
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"router.isReady dev mode isReady should be true immediately for getServerSideProps page with query",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"router.isReady dev mode isReady should be true immediately for getStaticProps page without query"
],
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"router.isReady production mode isReady should be true after query update for auto-export page with query",
"router.isReady production mode isReady should be true after query update for dynamic auto-export page with query",
"router.isReady production mode isReady should be true after query update for dynamic auto-export page without query",
"router.isReady production mode isReady should be true after query update for getStaticProps page with query",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"router.isReady production mode isReady should be true immediately for auto-export page without query",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"router.isReady production mode isReady should be true immediately for getInitialProps page",
"router.isReady production mode isReady should be true immediately for getInitialProps page with query",
"router.isReady production mode isReady should be true immediately for getServerSideProps page",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"router.isReady production mode isReady should be true immediately for getServerSideProps page with query",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"router.isReady production mode isReady should be true immediately for getStaticProps page without query"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/router-prefetch/test/index.test.js": {
"passed": [
"Router prefetch dev mode should not prefetch",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Router prefetch dev mode should resolve prefetch promise"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"Router prefetch production mode should resolve prefetch promise with invalid href"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
"runtimeError": false
},
"test/integration/router-rerender/test/index.test.js": {
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"passed": [
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"router rerender dev mode with middleware should not trigger unncessary rerenders when middleware is used"
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
],
update test manifest (#56522) update manifest from daily results Closes WEB-1728
2023-10-07 11:07:59 +02:00
"failed": [],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"pending": [
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"router rerender dev mode with rewrites should not trigger unncessary rerenders when rewrites are used",
"router rerender dev mode with rewrites should rerender with the correct query parameter if present with rewrites",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"router rerender production mode with middleware should not trigger unncessary rerenders when middleware is used",
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"router rerender production mode with rewrites should not trigger unncessary rerenders when rewrites are used",
"router rerender production mode with rewrites should rerender with the correct query parameter if present with rewrites"
],
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"test/integration/script-loader/test/index.test.js": {
"passed": [
"Next.js Script - Primary Strategies - Strict Mode Does not duplicate inline scripts",
"Next.js Script - Primary Strategies - Strict Mode onReady fires after load event and then on every subsequent re-mount",
"Next.js Script - Primary Strategies - Strict Mode onReady should only fires once after loaded (issue #39993)",
"Next.js Script - Primary Strategies - Strict Mode onload fires correctly",
"Next.js Script - Primary Strategies - Strict Mode priority afterInteractive",
"Next.js Script - Primary Strategies - Strict Mode priority beforeInteractive on navigate",
"Next.js Script - Primary Strategies - Strict Mode priority beforeInteractive with inline script",
"Next.js Script - Primary Strategies - Strict Mode priority beforeInteractive with inline script should execute",
"Next.js Script - Primary Strategies - Strict Mode priority lazyOnload"
],
"failed": [
"Next.js Script - Primary Strategies - Strict Mode priority beforeInteractive",
"Next.js Script - Primary Strategies - Strict Mode priority beforeInteractive - older version"
],
"pending": [
"Next.js Script - Primary Strategies - Production Mode production mode Does not duplicate inline scripts",
"Next.js Script - Primary Strategies - Production Mode production mode Error message is shown if Partytown is not installed locally",
"Next.js Script - Primary Strategies - Production Mode production mode onReady fires after load event and then on every subsequent re-mount",
"Next.js Script - Primary Strategies - Production Mode production mode onReady should only fires once after loaded (issue #39993)",
"Next.js Script - Primary Strategies - Production Mode production mode onload fires correctly",
"Next.js Script - Primary Strategies - Production Mode production mode priority afterInteractive",
"Next.js Script - Primary Strategies - Production Mode production mode priority beforeInteractive",
"Next.js Script - Primary Strategies - Production Mode production mode priority beforeInteractive - older version",
"Next.js Script - Primary Strategies - Production Mode production mode priority beforeInteractive on navigate",
"Next.js Script - Primary Strategies - Production Mode production mode priority beforeInteractive with inline script",
"Next.js Script - Primary Strategies - Production Mode production mode priority beforeInteractive with inline script should execute",
"Next.js Script - Primary Strategies - Production Mode production mode priority lazyOnload"
],
"flakey": [],
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/scroll-back-restoration/test/index.test.js": {
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"passed": [
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Scroll Back Restoration Support dev mode should restore the scroll position on navigating back"
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Scroll Back Restoration Support production mode should restore the scroll position on navigating back"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/scroll-forward-restoration/test/index.test.js": {
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"passed": [
"Scroll Forward Restoration Support dev mode should restore the scroll position on navigating forward"
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
],
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
update test manifest (#56938) Update test manifest from daily test run Closes WEB-1792
2023-10-20 02:43:56 +02:00
"Scroll Forward Restoration Support production mode should restore the scroll position on navigating forward"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/scss-modules/test/basic-scss.test.js": {
"passed": [
"Can hot reload CSS Module without losing state should update CSS color without remounting <input>",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Has CSS Module in computed styles in Development should have CSS for page"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
"pending": [
"3rd Party CSS Module Support production mode should have compiled successfully",
"3rd Party CSS Module Support production mode should've emitted a single CSS file",
"3rd Party CSS Module Support production mode should've injected the CSS on server render",
"Basic SCSS Module Support production mode should have compiled successfully",
"Basic SCSS Module Support production mode should've emitted a single CSS file",
"Basic SCSS Module Support production mode should've injected the CSS on server render",
"CSS Module Composes Usage (Basic) production mode should have compiled successfully",
"CSS Module Composes Usage (Basic) production mode should've emitted a single CSS file",
"CSS Module Composes Usage (External) production mode should have compiled successfully",
"CSS Module Composes Usage (External) production mode should've emitted a single CSS file",
"Has CSS Module in computed styles in Production production mode should have CSS for page",
"Has CSS Module in computed styles in Production production mode should have compiled successfully"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/scss-modules/test/dynamic-route.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"Catch-all Route CSS Module Usage production mode should apply styles correctly",
"Catch-all Route CSS Module Usage production mode should have compiled successfully",
"Catch-all Route CSS Module Usage production mode should've emitted a single CSS file",
"Dynamic Route CSS Module Usage production mode should apply styles correctly",
"Dynamic Route CSS Module Usage production mode should have compiled successfully",
"Dynamic Route CSS Module Usage production mode should've emitted a single CSS file"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/scss-modules/test/valid-invalid.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Invalid CSS Global Module Usage in node_modules production mode should fail to build",
"Invalid CSS Module Usage in node_modules production mode should fail to build",
"Valid CSS Module Usage from within node_modules production mode should have compiled successfully",
"Valid CSS Module Usage from within node_modules production mode should've emitted a single CSS file",
"Valid CSS Module Usage from within node_modules production mode should've prerendered with relevant data",
"Valid Nested CSS Module Usage from within node_modules production mode should have compiled successfully",
"Valid Nested CSS Module Usage from within node_modules production mode should've emitted a single CSS file",
"Valid Nested CSS Module Usage from within node_modules production mode should've prerendered with relevant data"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/scss/test/basic-global-support.test.js": {
"passed": [],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"failed": [],
"pending": [
"Basic Global Support scss production mode should compile successfully",
"Basic Global Support scss production mode should've emitted a single CSS file",
"Basic Global Support with src/ dir production mode should compile successfully",
"Basic Global Support with src/ dir production mode should've emitted a single CSS file",
"Basic Module Include Paths Support production mode should compile successfully",
"Basic Module Include Paths Support production mode should've emitted a single CSS file",
"Basic Module Prepend Data Support production mode should compile successfully",
"Basic Module Prepend Data Support production mode should've emitted a single CSS file",
"CSS Import from node_modules production mode should fail the build",
"Good CSS Import from node_modules production mode should compile successfully",
"Good CSS Import from node_modules production mode should've emitted a single CSS file",
"Good Nested CSS Import from node_modules production mode should compile successfully",
"Good Nested CSS Import from node_modules production mode should've emitted a single CSS file",
"Multi Global Support (reversed) production mode should compile successfully",
"Multi Global Support (reversed) production mode should've emitted a single CSS file",
"Multi Global Support production mode should compile successfully",
"Multi Global Support production mode should've emitted a single CSS file",
"Nested @import() Global Support production mode should compile successfully",
"Nested @import() Global Support production mode should've emitted a single CSS file"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/scss/test/basic-scss.test.js": {
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"passed": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"SCSS Support development mode Can hot reload CSS without losing state should update CSS color without remounting <input>"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
update manifest (#57468) update manifest for daily test run Closes WEB-1876
2023-10-26 07:21:59 +02:00
"failed": [],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"pending": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"SCSS Support production mode CSS Compilation and Prefixing should compile successfully",
"SCSS Support production mode CSS Compilation and Prefixing should've compiled and prefixed",
"SCSS Support production mode CSS Compilation and Prefixing should've emitted a source map",
"SCSS Support production mode Friendly Webpack Error should be a friendly error successfully",
"SCSS Support production mode Has CSS in computed styles in Production should have CSS for page",
"SCSS Support production mode Has CSS in computed styles in Production should have compiled successfully",
"SCSS Support production mode Has CSS in computed styles in Production should've preloaded the CSS file and injected it in <head>"
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/scss/test/css-and-styled-jsx.test.js": {
"passed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Ordering with styled-jsx (dev) should have the correct color (css ordering)"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Ordering with styled-jsx (prod) production mode should have compiled successfully",
"Ordering with styled-jsx (prod) production mode should have the correct color (css ordering)"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/scss/test/dev-css-handling.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Body is not hidden when broken in Development should have body visible",
"Body is not hidden when unused in Development should have body visible",
"Has CSS in computed styles in Development should have CSS for page"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/scss/test/scss-loader-handling.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"failed": [],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"pending": [
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"SCSS Support loader handling production mode CSS URL via `file-loader` and asset prefix (1) should compile successfully",
"SCSS Support loader handling production mode CSS URL via `file-loader` and asset prefix (1) should've emitted expected files",
"SCSS Support loader handling production mode CSS URL via `file-loader` and asset prefix (2) should compile successfully",
"SCSS Support loader handling production mode CSS URL via `file-loader` and asset prefix (2) should've emitted expected files",
"SCSS Support loader handling production mode CSS URL via `file-loader` should compile successfully",
"SCSS Support loader handling production mode CSS URL via `file-loader` should've emitted expected files",
"SCSS Support loader handling production mode CSS URL via file-loader sass partial should compile successfully",
"SCSS Support loader handling production mode CSS URL via file-loader sass partial should've emitted expected files",
"SCSS Support loader handling production mode Data Urls should compile successfully",
"SCSS Support loader handling production mode Data Urls should've emitted expected files",
"SCSS Support loader handling production mode External imports should compile successfully",
"SCSS Support loader handling production mode External imports should've emitted expected files",
"SCSS Support loader handling production mode Preprocessor loader order should compile successfully"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/scss/test/valid-invalid-scss.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Invalid Global CSS production mode should fail to build",
"Invalid Global CSS with Custom App production mode should fail to build",
"Invalid SCSS in _document production mode should fail to build",
"Valid and Invalid Global CSS with Custom App production mode should fail to build"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/server-asset-modules/test/index.test.js": {
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"passed": [
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"serverside asset modules dev mode should enable reading local files in api routes"
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"serverside asset modules production mode should enable reading local files in api routes"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/server-side-dev-errors/test/index.test.js": {
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"passed": [
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"server-side dev errors should show server-side error for api route correctly",
"server-side dev errors should show server-side error for dynamic api route correctly",
Update Turbopack test manifest (#58122) This auto-generated PR updates the integration test manifest used when testing Turbopack. Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-11-07 15:33:43 +01:00
"server-side dev errors should show server-side error for dynamic gssp page correctly",
"server-side dev errors should show server-side error for gsp page correctly",
test(integration): adjust fixture to work with turbopack (#59595)
2023-12-13 22:17:52 +01:00
"server-side dev errors should show server-side error for gssp page correctly",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"server-side dev errors should show server-side error for uncaught empty exception correctly",
"server-side dev errors should show server-side error for uncaught empty rejection correctly",
"server-side dev errors should show server-side error for uncaught exception correctly",
"server-side dev errors should show server-side error for uncaught rejection correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
test(integration): adjust fixture to work with turbopack (#59595)
2023-12-13 22:17:52 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/src-dir-support-double-dir/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic Routing dev mode should render from pages",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Dynamic Routing dev mode should render not render from src/pages"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic Routing production mode should render from pages",
"Dynamic Routing production mode should render not render from src/pages"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/src-dir-support/test/index.test.js": {
"passed": [
"Dynamic Routing dev mode should navigate to a dynamic page successfully",
"Dynamic Routing dev mode should navigate to a nested dynamic page successfully",
"Dynamic Routing dev mode should pass params in getInitialProps during SSR",
"Dynamic Routing dev mode should prioritize a non-dynamic page",
"Dynamic Routing dev mode should render another normal route",
"Dynamic Routing dev mode should render dynamic page",
"Dynamic Routing dev mode should render nested dynamic page",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Dynamic Routing dev mode should render normal route"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Dynamic Routing production mode should navigate to a dynamic page successfully",
"Dynamic Routing production mode should navigate to a nested dynamic page successfully",
"Dynamic Routing production mode should pass params in getInitialProps during SSR",
"Dynamic Routing production mode should prioritize a non-dynamic page",
"Dynamic Routing production mode should render another normal route",
"Dynamic Routing production mode should render dynamic page",
"Dynamic Routing production mode should render nested dynamic page",
"Dynamic Routing production mode should render normal route"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/ssg-data-404/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"SSG data 404 dev mode should hard navigate when a new deployment occurs"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
"SSG data 404 production mode should hard navigate when a new deployment occurs"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/ssg-dynamic-routes-404-page/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Custom 404 Page for static site generation with dynamic routes dev mode should respond to a not existing page with 404"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
"failed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"pending": [
"Custom 404 Page for static site generation with dynamic routes production mode should build successfully",
"Custom 404 Page for static site generation with dynamic routes production mode should respond to a not existing page with 404"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/static-404/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"Static 404 page With config enabled production mode should export 404 page without custom _error",
"Static 404 page With config enabled production mode should not export 404 page with custom _error GIP",
"Static 404 page With config enabled production mode should not export 404 page with getInitialProps in _app"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/static-page-name/test/index.test.js": {
"passed": [
"Static Page Name dev mode should navigate to static page name correctly",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Static Page Name dev mode should render the page via SSR correctly"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Static Page Name production mode should navigate to static page name correctly",
"Static Page Name production mode should render the page via SSR correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/styled-jsx-plugin/test/index.test.js": {
"passed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"styled-jsx using in node_modules production mode should serve a page correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/telemetry/test/config.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"config telemetry production mode detects i18n and image configs for session start",
"config telemetry production mode detects output config for session start",
"config telemetry production mode detects rewrites, headers, and redirects for next build",
"config telemetry production mode emits telemery for usage of optimizeFonts, image, script & dynamic",
"config telemetry production mode emits telemetry for `next lint`",
"config telemetry production mode emits telemetry for lint during build",
"config telemetry production mode emits telemetry for lint during build when '--no-lint' is specified",
"config telemetry production mode emits telemetry for lint during build when 'ignoreDuringBuilds' is specified",
"config telemetry production mode emits telemetry for middleware related options",
"config telemetry production mode emits telemetry for transpilePackages",
"config telemetry production mode emits telemetry for usage of @vercel/og",
"config telemetry production mode emits telemetry for usage of `nextScriptWorkers`",
"config telemetry production mode emits telemetry for usage of `optimizeCss`",
"config telemetry production mode emits telemetry for usage of middleware",
"config telemetry production mode emits telemetry for usage of next/legacy/image",
"config telemetry production mode emits telemetry for usage of swc",
"config telemetry production mode emits telemetry for usage of swc plugins"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/telemetry/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Telemetry CLI can disable telemetry with env NEXT_TELEMETRY_DISABLED",
"Telemetry CLI can disable telemetry with flag",
"Telemetry CLI can disable telemetry without flag",
"Telemetry CLI can enable telemetry with flag",
"Telemetry CLI can enable telemetry without flag",
"Telemetry CLI can print telemetry status",
"Telemetry CLI can re-disable telemetry",
"Telemetry CLI can re-enable telemetry",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"Telemetry CLI detects isSrcDir dir correctly for `next dev`"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"Telemetry CLI production mode cli session: babel tooling config",
"Telemetry CLI production mode cli session: custom babel config (plugin)",
"Telemetry CLI production mode cli session: custom babel config (preset)",
"Telemetry CLI production mode cli session: next config with webpack",
"Telemetry CLI production mode cli session: package.json custom babel config (plugin)",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"Telemetry CLI production mode detect page counts correctly for `next build`",
Update Turbopack test manifest (#59326) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-06 14:49:58 +01:00
"Telemetry CLI production mode detect static 404 correctly for `next build`",
"Telemetry CLI production mode detects correct cli session defaults",
"Telemetry CLI production mode detects isSrcDir dir correctly for `next build`",
"Telemetry CLI production mode detects tests correctly for `next build`",
"Telemetry CLI production mode emits event when swc fails to load",
"Telemetry CLI production mode logs completed `next build` with warnings"
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/telemetry/test/page-features.test.js": {
"passed": [
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"page features telemetry detects --turbo correctly for `next dev`",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"page features telemetry detects --turbo correctly for `next dev` stopped"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/trailing-slash-dist/test/index.test.js": {
"passed": ["Trailing slash in distDir dev mode supports trailing slash"],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/trailing-slashes-href-resolving/test/index.test.js": {
"passed": [
"href resolving trailing-slash dev mode should route to /another/ correctly",
"href resolving trailing-slash dev mode should route to /blog/another/ correctly",
"href resolving trailing-slash dev mode should route to /blog/first-post/ correctly",
"href resolving trailing-slash dev mode should route to /catch-all/first/ correctly",
"href resolving trailing-slash dev mode should route to /catch-all/hello/world/ correctly",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"href resolving trailing-slash dev mode should route to /top-level-slug/ correctly"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"href resolving trailing-slash production mode should preload SSG routes correctly",
"href resolving trailing-slash production mode should route to /another/ correctly",
"href resolving trailing-slash production mode should route to /blog/another/ correctly",
"href resolving trailing-slash production mode should route to /blog/first-post/ correctly",
"href resolving trailing-slash production mode should route to /catch-all/first/ correctly",
"href resolving trailing-slash production mode should route to /catch-all/hello/world/ correctly",
"href resolving trailing-slash production mode should route to /top-level-slug/ correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/trailing-slashes-rewrite/test/index.test.js": {
"passed": [
"Trailing Slash Rewrite Proxying dev mode should proxy non-existent page correctly",
"Trailing Slash Rewrite Proxying dev mode should resolve a catch-all page correctly",
"Trailing Slash Rewrite Proxying dev mode should resolve a dynamic page correctly",
"Trailing Slash Rewrite Proxying dev mode should resolve index page correctly",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Trailing Slash Rewrite Proxying dev mode should resolve products page correctly"
],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Trailing Slash Rewrite Proxying production mode should proxy non-existent page correctly",
"Trailing Slash Rewrite Proxying production mode should resolve a catch-all page correctly",
"Trailing Slash Rewrite Proxying production mode should resolve a dynamic page correctly",
"Trailing Slash Rewrite Proxying production mode should resolve index page correctly",
"Trailing Slash Rewrite Proxying production mode should resolve products page correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/trailing-slashes/test/index.test.js": {
"passed": [
"Trailing slashes dev mode, trailingSlash: false / should client side render /index.js, with router path /",
"Trailing slashes dev mode, trailingSlash: false / should resolve to /index.js, with router path /",
"Trailing slashes dev mode, trailingSlash: false /about should client side render /about.js, with router path /about",
"Trailing slashes dev mode, trailingSlash: false /about should resolve to /about.js, with router path /about",
"Trailing slashes dev mode, trailingSlash: false /about/ should redirect to /about",
"Trailing slashes dev mode, trailingSlash: false /about?hello=world should client side render /about.js, with router path /about",
"Trailing slashes dev mode, trailingSlash: false /about?hello=world should resolve to /about.js, with router path /about",
"Trailing slashes dev mode, trailingSlash: false /catch-all/hello.world/ should redirect to /catch-all/hello.world",
"Trailing slashes dev mode, trailingSlash: false /catch-all/hello/world should client side render /catch-all/[...slug].js, with router path /catch-all/[...slug]",
"Trailing slashes dev mode, trailingSlash: false /catch-all/hello/world should resolve to /catch-all/[...slug].js, with router path /catch-all/[...slug]",
"Trailing slashes dev mode, trailingSlash: false /catch-all/hello/world/ should redirect to /catch-all/hello/world",
"Trailing slashes dev mode, trailingSlash: false /external-linker?href=https://nextjs.org should have href https://nextjs.org",
"Trailing slashes dev mode, trailingSlash: false /external-linker?href=https://nextjs.org/ should have href https://nextjs.org/",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/ should have href /",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/ should navigate to /",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/ should push route to /",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/about should have href /about",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/about should navigate to /about",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/about should push route to /about",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/about/ should have href /about",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/about/ should navigate to /about",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/about/ should push route to /about",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/about/?hello=world should have href /about?hello=world",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/about/?hello=world should navigate to /about?hello=world",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/about/?hello=world should push route to /about?hello=world",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/about?hello=world should have href /about?hello=world",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/about?hello=world should navigate to /about?hello=world",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/about?hello=world should push route to /about?hello=world",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/catch-all/hello.world/ should have href /catch-all/hello.world",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/catch-all/hello.world/ should navigate to /catch-all/hello.world",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/catch-all/hello.world/ should push route to /catch-all/hello.world",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/catch-all/hello/ should have href /catch-all/hello",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/catch-all/hello/ should navigate to /catch-all/hello",
"Trailing slashes dev mode, trailingSlash: false /linker?href=/catch-all/hello/ should push route to /catch-all/hello",
"Trailing slashes dev mode, trailingSlash: true / should client side render /index.js, with router path /",
"Trailing slashes dev mode, trailingSlash: true / should resolve to /index.js, with router path /",
"Trailing slashes dev mode, trailingSlash: true /about should redirect to /about/",
"Trailing slashes dev mode, trailingSlash: true /about/ should client side render /about.js, with router path /about",
"Trailing slashes dev mode, trailingSlash: true /about/ should resolve to /about.js, with router path /about",
"Trailing slashes dev mode, trailingSlash: true /about/?hello=world should client side render /about.js, with router path /about",
"Trailing slashes dev mode, trailingSlash: true /about/?hello=world should resolve to /about.js, with router path /about",
"Trailing slashes dev mode, trailingSlash: true /catch-all/hello.world/ should redirect to /catch-all/hello.world",
"Trailing slashes dev mode, trailingSlash: true /catch-all/hello/world should redirect to /catch-all/hello/world/",
"Trailing slashes dev mode, trailingSlash: true /catch-all/hello/world/ should client side render /catch-all/[...slug].js, with router path /catch-all/[...slug]",
"Trailing slashes dev mode, trailingSlash: true /catch-all/hello/world/ should resolve to /catch-all/[...slug].js, with router path /catch-all/[...slug]",
"Trailing slashes dev mode, trailingSlash: true /external-linker?href=https://nextjs.org should have href https://nextjs.org",
"Trailing slashes dev mode, trailingSlash: true /external-linker?href=https://nextjs.org/ should have href https://nextjs.org/",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/ should have href /",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/ should navigate to /",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/ should push route to /",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Trailing slashes dev mode, trailingSlash: true /linker?href=/about should have href /about/",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/about should navigate to /about/",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/about should push route to /about/",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/about/ should have href /about/",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/about/ should navigate to /about/",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/about/ should push route to /about/",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/about/?hello=world should have href /about/?hello=world",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/about/?hello=world should navigate to /about/?hello=world",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/about/?hello=world should push route to /about/?hello=world",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/about?hello=world should have href /about/?hello=world",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/about?hello=world should navigate to /about/?hello=world",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/about?hello=world should push route to /about/?hello=world",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Trailing slashes dev mode, trailingSlash: true /linker?href=/catch-all/hello.world/ should have href /catch-all/hello.world",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/catch-all/hello.world/ should navigate to /catch-all/hello.world",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/catch-all/hello.world/ should push route to /catch-all/hello.world",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Trailing slashes dev mode, trailingSlash: true /linker?href=/catch-all/hello/ should have href /catch-all/hello/",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/catch-all/hello/ should navigate to /catch-all/hello/",
"Trailing slashes dev mode, trailingSlash: true /linker?href=/catch-all/hello/ should push route to /catch-all/hello/",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Trailing slashes dev mode, with basepath, trailingSlash: true /docs should redirect to /docs/",
"Trailing slashes dev mode, with basepath, trailingSlash: true /docs/about should redirect to /docs/about/",
"Trailing slashes dev mode, with basepath, trailingSlash: true /docs/catch-all/hello.world/ should redirect to /docs/catch-all/hello.world",
"Trailing slashes dev mode, with basepath, trailingSlash: true /docs/catch-all/hello/world should redirect to /docs/catch-all/hello/world/",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Trailing slashes dev mode, with basepath, trailingSlash: true /docs/linker?href=/ should have href /docs/",
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"Trailing slashes dev mode, with basepath, trailingSlash: true /docs/linker?href=/ should navigate to /docs/",
"Trailing slashes dev mode, with basepath, trailingSlash: true /docs/linker?href=/ should push route to /docs/",
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"Trailing slashes dev mode, with basepath, trailingSlash: true /docs/linker?href=/about should have href /docs/about/",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"Trailing slashes dev mode, with basepath, trailingSlash: true /docs/linker?href=/about should navigate to /docs/about/",
"Trailing slashes dev mode, with basepath, trailingSlash: true /docs/linker?href=/about should push route to /docs/about/"
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Trailing slashes production mode, trailingSlash: false / should client side render /index.js, with router path /",
"Trailing slashes production mode, trailingSlash: false / should resolve to /index.js, with router path /",
"Trailing slashes production mode, trailingSlash: false /about should client side render /about.js, with router path /about",
"Trailing slashes production mode, trailingSlash: false /about should resolve to /about.js, with router path /about",
"Trailing slashes production mode, trailingSlash: false /about/ should redirect to /about",
"Trailing slashes production mode, trailingSlash: false /about?hello=world should client side render /about.js, with router path /about",
"Trailing slashes production mode, trailingSlash: false /about?hello=world should resolve to /about.js, with router path /about",
"Trailing slashes production mode, trailingSlash: false /catch-all/hello.world/ should redirect to /catch-all/hello.world",
"Trailing slashes production mode, trailingSlash: false /catch-all/hello/world should client side render /catch-all/[...slug].js, with router path /catch-all/[...slug]",
"Trailing slashes production mode, trailingSlash: false /catch-all/hello/world should resolve to /catch-all/[...slug].js, with router path /catch-all/[...slug]",
"Trailing slashes production mode, trailingSlash: false /catch-all/hello/world/ should redirect to /catch-all/hello/world",
"Trailing slashes production mode, trailingSlash: false /external-linker?href=https://nextjs.org should have href https://nextjs.org",
"Trailing slashes production mode, trailingSlash: false /external-linker?href=https://nextjs.org/ should have href https://nextjs.org/",
"Trailing slashes production mode, trailingSlash: false /linker?href=/ should have href /",
"Trailing slashes production mode, trailingSlash: false /linker?href=/ should navigate to /",
"Trailing slashes production mode, trailingSlash: false /linker?href=/ should push route to /",
"Trailing slashes production mode, trailingSlash: false /linker?href=/about should have href /about",
"Trailing slashes production mode, trailingSlash: false /linker?href=/about should navigate to /about",
"Trailing slashes production mode, trailingSlash: false /linker?href=/about should push route to /about",
"Trailing slashes production mode, trailingSlash: false /linker?href=/about/ should have href /about",
"Trailing slashes production mode, trailingSlash: false /linker?href=/about/ should navigate to /about",
"Trailing slashes production mode, trailingSlash: false /linker?href=/about/ should push route to /about",
"Trailing slashes production mode, trailingSlash: false /linker?href=/about/?hello=world should have href /about?hello=world",
"Trailing slashes production mode, trailingSlash: false /linker?href=/about/?hello=world should navigate to /about?hello=world",
"Trailing slashes production mode, trailingSlash: false /linker?href=/about/?hello=world should push route to /about?hello=world",
"Trailing slashes production mode, trailingSlash: false /linker?href=/about?hello=world should have href /about?hello=world",
"Trailing slashes production mode, trailingSlash: false /linker?href=/about?hello=world should navigate to /about?hello=world",
"Trailing slashes production mode, trailingSlash: false /linker?href=/about?hello=world should push route to /about?hello=world",
"Trailing slashes production mode, trailingSlash: false /linker?href=/catch-all/hello.world/ should have href /catch-all/hello.world",
"Trailing slashes production mode, trailingSlash: false /linker?href=/catch-all/hello.world/ should navigate to /catch-all/hello.world",
"Trailing slashes production mode, trailingSlash: false /linker?href=/catch-all/hello.world/ should push route to /catch-all/hello.world",
"Trailing slashes production mode, trailingSlash: false /linker?href=/catch-all/hello/ should have href /catch-all/hello",
"Trailing slashes production mode, trailingSlash: false /linker?href=/catch-all/hello/ should navigate to /catch-all/hello",
"Trailing slashes production mode, trailingSlash: false /linker?href=/catch-all/hello/ should push route to /catch-all/hello",
"Trailing slashes production mode, trailingSlash: false should have a redirect in the routesmanifest",
"Trailing slashes production mode, trailingSlash: true / should client side render /index.js, with router path /",
"Trailing slashes production mode, trailingSlash: true / should resolve to /index.js, with router path /",
"Trailing slashes production mode, trailingSlash: true /about should redirect to /about/",
"Trailing slashes production mode, trailingSlash: true /about/ should client side render /about.js, with router path /about",
"Trailing slashes production mode, trailingSlash: true /about/ should resolve to /about.js, with router path /about",
"Trailing slashes production mode, trailingSlash: true /about/?hello=world should client side render /about.js, with router path /about",
"Trailing slashes production mode, trailingSlash: true /about/?hello=world should resolve to /about.js, with router path /about",
"Trailing slashes production mode, trailingSlash: true /catch-all/hello.world/ should redirect to /catch-all/hello.world",
"Trailing slashes production mode, trailingSlash: true /catch-all/hello/world should redirect to /catch-all/hello/world/",
"Trailing slashes production mode, trailingSlash: true /catch-all/hello/world/ should client side render /catch-all/[...slug].js, with router path /catch-all/[...slug]",
"Trailing slashes production mode, trailingSlash: true /catch-all/hello/world/ should resolve to /catch-all/[...slug].js, with router path /catch-all/[...slug]",
"Trailing slashes production mode, trailingSlash: true /external-linker?href=https://nextjs.org should have href https://nextjs.org",
"Trailing slashes production mode, trailingSlash: true /external-linker?href=https://nextjs.org/ should have href https://nextjs.org/",
"Trailing slashes production mode, trailingSlash: true /linker?href=/ should have href /",
"Trailing slashes production mode, trailingSlash: true /linker?href=/ should navigate to /",
"Trailing slashes production mode, trailingSlash: true /linker?href=/ should push route to /",
"Trailing slashes production mode, trailingSlash: true /linker?href=/about should have href /about/",
"Trailing slashes production mode, trailingSlash: true /linker?href=/about should navigate to /about/",
"Trailing slashes production mode, trailingSlash: true /linker?href=/about should push route to /about/",
"Trailing slashes production mode, trailingSlash: true /linker?href=/about/ should have href /about/",
"Trailing slashes production mode, trailingSlash: true /linker?href=/about/ should navigate to /about/",
"Trailing slashes production mode, trailingSlash: true /linker?href=/about/ should push route to /about/",
"Trailing slashes production mode, trailingSlash: true /linker?href=/about/?hello=world should have href /about/?hello=world",
"Trailing slashes production mode, trailingSlash: true /linker?href=/about/?hello=world should navigate to /about/?hello=world",
"Trailing slashes production mode, trailingSlash: true /linker?href=/about/?hello=world should push route to /about/?hello=world",
"Trailing slashes production mode, trailingSlash: true /linker?href=/about?hello=world should have href /about/?hello=world",
"Trailing slashes production mode, trailingSlash: true /linker?href=/about?hello=world should navigate to /about/?hello=world",
"Trailing slashes production mode, trailingSlash: true /linker?href=/about?hello=world should push route to /about/?hello=world",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Trailing slashes production mode, trailingSlash: true /linker?href=/catch-all/hello.world/ should have href /catch-all/hello.world",
"Trailing slashes production mode, trailingSlash: true /linker?href=/catch-all/hello.world/ should navigate to /catch-all/hello.world",
"Trailing slashes production mode, trailingSlash: true /linker?href=/catch-all/hello.world/ should push route to /catch-all/hello.world",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Trailing slashes production mode, trailingSlash: true /linker?href=/catch-all/hello/ should have href /catch-all/hello/",
"Trailing slashes production mode, trailingSlash: true /linker?href=/catch-all/hello/ should navigate to /catch-all/hello/",
"Trailing slashes production mode, trailingSlash: true /linker?href=/catch-all/hello/ should push route to /catch-all/hello/",
add flakey test (#56080) It's flakey for turbopack Closes WEB-1671 Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2023-09-27 13:24:35 +02:00
"Trailing slashes production mode, trailingSlash: true should have a trailing redirect in the routesmanifest",
Turbopack: update test manifest (#56026) Update from daily test run also enabled a lot more tests marked some tests flakey Closes WEB-1658
2023-09-26 18:28:48 +02:00
"Trailing slashes production mode, with basepath, trailingSlash: true /docs should redirect to /docs/",
"Trailing slashes production mode, with basepath, trailingSlash: true /docs/about should redirect to /docs/about/",
"Trailing slashes production mode, with basepath, trailingSlash: true /docs/catch-all/hello.world/ should redirect to /docs/catch-all/hello.world",
"Trailing slashes production mode, with basepath, trailingSlash: true /docs/catch-all/hello/world should redirect to /docs/catch-all/hello/world/",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Trailing slashes production mode, with basepath, trailingSlash: true /docs/linker?href=/ should have href /docs/",
"Trailing slashes production mode, with basepath, trailingSlash: true /docs/linker?href=/ should navigate to /docs/",
"Trailing slashes production mode, with basepath, trailingSlash: true /docs/linker?href=/ should push route to /docs/",
"Trailing slashes production mode, with basepath, trailingSlash: true /docs/linker?href=/about should have href /docs/about/",
"Trailing slashes production mode, with basepath, trailingSlash: true /docs/linker?href=/about should navigate to /docs/about/",
"Trailing slashes production mode, with basepath, trailingSlash: true /docs/linker?href=/about should push route to /docs/about/"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
update turbopack test manifest (#57357)
2023-10-24 22:33:38 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/tsconfig-verifier/test/index.test.js": {
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"passed": [],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"tsconfig.json verifier Creates a default tsconfig.json when one is missing",
"tsconfig.json verifier Updates an existing tsconfig.json without losing comments",
"tsconfig.json verifier Works with an empty tsconfig.json (docs)",
"tsconfig.json verifier allows you to extend another configuration file",
"tsconfig.json verifier allows you to set bundler moduleResolution mode",
"tsconfig.json verifier allows you to set commonjs module mode",
"tsconfig.json verifier allows you to set es2020 module mode",
"tsconfig.json verifier allows you to set node16 module mode",
"tsconfig.json verifier allows you to set node16 moduleResolution mode",
"tsconfig.json verifier allows you to set target mode",
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"tsconfig.json verifier allows you to set verbatimModuleSyntax true via extends without adding isolatedModules",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"tsconfig.json verifier allows you to set verbatimModuleSyntax true without adding isolatedModules",
"tsconfig.json verifier creates compilerOptions when you extend another config"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/turbopack-unsupported-log/index.test.ts": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"turbopack unsupported features log should not warn by default",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"turbopack unsupported features log should not warn with empty next.config.js",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"turbopack unsupported features log should warn with next.config.js with unsupported field"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/turbotrace-with-webpack-worker/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"build trace with extra entries production mode should build and trace correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/typeof-window-replace/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"typeof window replace production mode Does not replace `typeof window` for `node_modules` code",
"typeof window replace production mode Replaces `typeof window` with object for client code",
"typeof window replace production mode Replaces `typeof window` with undefined for server code"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/typescript-app-type-declarations/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"TypeScript App Type Declarations should not touch an existing correct next-env.d.ts",
"TypeScript App Type Declarations should overwrite next-env.d.ts if an incorrect one exists",
"TypeScript App Type Declarations should write a new next-env.d.ts if none exist"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/typescript-baseurl/test/index.test.js": {
"passed": ["TypeScript Features default behavior should render the page"],
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/typescript-custom-tsconfig/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
"Custom TypeScript Config production mode should warn when using custom typescript path"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/typescript-external-dir/project/test/index.test.js": {
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"TypeScript Features default behavior should render the page with external TS/TSX dependencies"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"failed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/typescript-filtered-files/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"TypeScript filtered files production mode should fail to build the app with a file named con*test*.js"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/typescript-hmr/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"TypeScript HMR delete a page and add it back should detect the changes to typescript pages and display it",
"TypeScript HMR should ignore type errors in development"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
invert test filtering logic to exclude known failing (#56663) ### What? instead of include known passing tests also updates the update test manifest ### Why? Newly added test cases should always pass turbopack (or at least you would need to manually opt-out of it. ### How? Uses a exclude list of tests instead of an allow list Closes WEB-1752
2023-10-10 20:26:40 +02:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": ["TypeScript HMR should recover from a type error"],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/typescript-ignore-errors/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
"TypeScript with error handling options production mode ignoreBuildErrors: false Next fails to build the application despite type errors in incremental mode",
"TypeScript with error handling options production mode ignoreBuildErrors: false Next fails to build the application despite type errors without incremental mode",
"TypeScript with error handling options production mode ignoreBuildErrors: true Next builds the application despite type errors in incremental mode",
"TypeScript with error handling options production mode ignoreBuildErrors: true Next builds the application despite type errors without incremental mode"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/typescript-only-remove-type-imports/test/index.test.js": {
"passed": [],
"failed": [
"TypeScript onlyRemoveTypeImports dev mode should render a normal page correctly",
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
"TypeScript onlyRemoveTypeImports dev mode should render a page with type import correctly"
],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"TypeScript onlyRemoveTypeImports production mode should render a normal page correctly",
"TypeScript onlyRemoveTypeImports production mode should render a page with type import correctly"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/typescript-paths/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"typescript paths default behavior should alias components",
"typescript paths default behavior should resolve a single matching alias",
"typescript paths default behavior should resolve the first item in the array first",
"typescript paths default behavior should resolve the second item in as a fallback",
"typescript paths without baseurl default behavior should alias components",
"typescript paths without baseurl default behavior should resolve a single matching alias",
"typescript paths without baseurl default behavior should resolve the first item in the array first",
"typescript paths without baseurl default behavior should resolve the second item in as a fallback"
],
"failed": [
"typescript paths default behavior should not resolve to .d.ts files",
"typescript paths without baseurl default behavior should not resolve to .d.ts files"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/typescript-workspaces-paths/packages/www/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"TypeScript Features default behavior should alias components",
"TypeScript Features default behavior should resolve a single matching alias",
"TypeScript Features default behavior should resolve the first item in the array first",
"TypeScript Features default behavior should resolve the second item in as a fallback"
],
"failed": [
"TypeScript Features default behavior should not resolve to .d.ts files"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/typescript/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"TypeScript Features default behavior should not fail to render when an inactive page has an error",
"TypeScript Features default behavior should render the cookies page",
"TypeScript Features default behavior should render the cookies page with cookies",
"TypeScript Features default behavior should render the generics page",
"TypeScript Features default behavior should render the page",
"TypeScript Features default behavior should respond to async API route correctly",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"TypeScript Features default behavior should respond to sync API route correctly"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
"failed": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"TypeScript Features default behavior should render the angle bracket type assertions page",
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"TypeScript Features default behavior should resolve files in correct order"
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
],
"pending": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"TypeScript Features default behavior should report type checking to stdout",
"TypeScript Features production mode should build the app",
"TypeScript Features production mode should build the app with functions in next.config.js",
"TypeScript Features production mode should compile with different types should compile async getInitialProps for _error",
"TypeScript Features production mode should compile with different types should compile sync getStaticPaths & getStaticProps",
"TypeScript Features production mode should not inform when using default tsconfig path"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/undefined-webpack-config/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"failed": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"pending": [
Update Turbopack test manifest (#59798) This auto-generated PR updates the integration test manifest used when testing Turbopack.
2023-12-20 11:22:56 +01:00
"undefined webpack config error production mode should show in production mode",
"undefined webpack config error should show in dev mode"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/url-imports/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"failed": [],
"pending": [
"Handle url imports with next build should allow url import in css",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Handle url imports with next build should client-render the /ssg page",
"Handle url imports with next build should client-render the /ssr page",
"Handle url imports with next build should client-render the /static page",
"Handle url imports with next build should render a static url image import",
"Handle url imports with next build should render the /ssg page",
"Handle url imports with next build should render the /ssr page",
"Handle url imports with next build should render the /static page",
"Handle url imports with next build should respond on value api",
"Handle url imports with next dev should allow url import in css",
"Handle url imports with next dev should client-render the /ssg page",
"Handle url imports with next dev should client-render the /ssr page",
"Handle url imports with next dev should client-render the /static page",
"Handle url imports with next dev should render a static url image import",
"Handle url imports with next dev should render the /ssg page",
"Handle url imports with next dev should render the /ssr page",
"Handle url imports with next dev should render the /static page",
"Handle url imports with next dev should respond on value api"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/url/test/index.test.js": {
fix(next-core): correct assets url reference condition (#58101) ### What Corrects how urlassetreference reads its assets path to allow to resolve image assets correctly. There is a test failure in the integration/url still, that involves probably larger refactoring so making this PR first to enable baseline, ensure further refactoring does not breaks anything.
2023-11-07 17:12:41 +01:00
"passed": [
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"Handle new URL asset references in next dev should client-render the /ssg page",
"Handle new URL asset references in next dev should client-render the /ssr page",
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Handle new URL asset references in next dev should client-render the /static page",
"Handle new URL asset references in next dev should render the /ssg page",
"Handle new URL asset references in next dev should render the /ssr page",
"Handle new URL asset references in next dev should render the /static page",
Update rust-toolchain to 2023-11-16 (#58558) This updates the rust toolchain to 2023-11-16 and: - Removes now-unnecessary `#![feature(async_fn_in_trait)]` - Applies auto-fixable lint fixes - Uses `Cargo.toml` new `lint` section instead of command line rustc flags Test Plan: Tested with updated turbo in a create-next-app Closes PACK-1979 Co-authored-by: OJ Kwon <1210596+kwonoj@users.noreply.github.com>
2023-11-18 01:29:50 +01:00
"Handle new URL asset references in next dev should respond on basename api",
Update Turbopack test manifest (#59109) This auto-generated PR updates the integration test manifest used when testing Turbopack. --------- Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
2023-12-01 11:16:28 +01:00
"Handle new URL asset references in next dev should respond on size api"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
build(cargo): bump up turbopack (#59032) ### What? Bump up turbopack which includes url rewrite related improvements. This makes `test/integration/url` test passes. Note there are some lacking behavior around edge runtime + url behavior, it is being tracked in PACK-2014. Closes PACK-2051
2023-11-28 21:42:26 +01:00
"failed": [],
update test mainfest (#56214) Closes WEB-1687
2023-10-02 08:45:50 +02:00
"pending": [
"Handle new URL asset references in next build should client-render the /ssg page",
"Handle new URL asset references in next build should client-render the /ssr page",
"Handle new URL asset references in next build should client-render the /static page",
"Handle new URL asset references in next build should render the /ssg page",
"Handle new URL asset references in next build should render the /ssr page",
"Handle new URL asset references in next build should render the /static page",
"Handle new URL asset references in next build should respond on basename api",
"Handle new URL asset references in next build should respond on size api"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/webpack-config-extensionalias/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"webpack config with extensionAlias setting should run correctly with an tsx file import with .js extension"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/webpack-config-mainjs/test/index.test.js": {
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"passed": [],
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Customized webpack config with main.js should run correctly with main.js customized"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/webpack-require-hook/test/index.test.js": {
"passed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"failed": [],
"pending": [
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"Handles Webpack Require Hook build Does not error during build",
"Handles Webpack Require Hook dev mode Applies and does not error during development"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/with-electron/test/index.test.js": {
"passed": [
"Should skip testing electron without process.env.TEST_ELECTRON set"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
"pending": [],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
},
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"test/integration/with-router/test/index.test.js": {
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"passed": [
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"withRouter SSR should show an error when trying to use router methods during SSR"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"failed": [],
test: add flaky turbopack integration tests to manifest (#56309)
2023-10-03 00:53:09 +02:00
"pending": [
"withRouter production mode allows observation of navigation events using top level Router",
"withRouter production mode allows observation of navigation events using top level Router deprecated behavior",
"withRouter production mode allows observation of navigation events using withRouter"
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Ensure Turbopack passing test list is sorted (#55948) I noticed that running the script to pull in the results wasn't deterministic between test runs, this ensures the list, passing, pending, and errors are all sorted, which makes the diff only include what actually changed between runs. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Adding or Updating Examples - The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # -->
2023-09-25 12:59:26 +02:00
"runtimeError": false
},
"test/integration/worker-webpack5/test/index.test.js": {
"passed": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"failed": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Web Workers with webpack 5 dev mode should pass on both client and worker"
turbopack: Add more skipped tests (#56052) Adds more flakey tests to the skipped turbopack list. Closes WEB-1662
2023-09-27 00:45:44 +02:00
],
"pending": [
Turbopack: update test manifest (#56133) Closes WEB-1672
2023-09-28 08:23:26 +02:00
"Web Workers with webpack 5 production mode should pass on both client and worker"
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
],
turbopack: only skip known flakey test cases (#55976) ### What? A follow up to https://github.com/vercel/next.js/pull/55975, this will list every flakey test in the turbopack suite so that we can run the remaining passing tests. ### Why? More tests is more better. ### How? Trial and error. Gonna let CI tell me what's flakey with a few runs. Closes WEB-1651
2023-09-26 16:58:34 +02:00
"flakey": [],
Allow filtering individual test cases inside test files (#55786) ### What? Updates `run-test.js` to allow running individual test cases inside a test file. ### Why? So that we can dramatically increase Turbopack's test coverage. Turbopack has implemented most (but not all) necessary features from the webpack bundles. But a single failing test case would prevent us from running any case inside a test file. With case filtering, we're able to run the cases we know will pass and prevent regressions on those. ### How? Case filtering is only exposed via the `NEXT_EXTERNAL_TESTS_FILTERS` ENV, which points to a JSON file containing a map of test files with the test cases inside those files that are known to pass. The known-passing test cases can be updated after Turbopack's daily integration test run by running `test/build-turbopack-tests-manifest.js`, which will update the `test/turbopack-tests-manifest.json` manifest. Closes WEB-1640 Co-authored-by: Tobias Koppers <1365881+sokra@users.noreply.github.com>
2023-09-22 23:37:48 +02:00
"runtimeError": false
}
}
Reference in a new issue Copy permalink